CVE-2026-33022

Tekton Pipelines: Controller can panic when setting long resolver names in TaskRun/PipelineRun

MEDIUM

6.5

CVSS Score

Published: March 20, 2026 at 07:48 AM UTC

Updated: June 17, 2026 at 10:36 AM UTC

2 products affected across 2 vendorsTekton PipelinesPipeline

Using pipeline by tektoncd?

Get instant alerts when new vulnerabilities affect pipeline - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM6.5

Exploit prediction

EPSS 0.4%

SSVC

No known exploit

Description

Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Versions 0.60.0 through 1.0.0, 1.1.0 through 1.3.2, 1.4.0 through 1.6.0, 1.7.0 through 1.9.0, 1.10.0, and 1.10.1 have a denial-of-service vulnerability in that allows any user who can create a TaskRun or PipelineRun to crash the controller cluster-wide by setting .spec.taskRef.resolver (or .spec.pipelineRef.resolver) to a string of 31+ characters. The crash occurs because GenerateDeterministicNameFromSpec produces a name exceeding the 63-character DNS-1123 label limit, and its truncation logic panics on a [-1] slice bound since the generated name contains no spaces. Once crashed, the controller enters a CrashLoopBackOff on restart (as it re-reconciles the offending resource), blocking all CI/CD reconciliation until the resource is manually deleted. Built-in resolvers (git, cluster, bundles, hub) are unaffected due to their short names, but any custom resolver name triggers the bug. The fix truncates the resolver-name prefix instead of the full string, preserving the hash suffix for determinism and uniqueness. This issue has been patched in versions 1.0.1, 1.3.3, 1.6.1, 1.9.2 and 1.10.2.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Tekton Pipelines · Linuxfoundationgo

95%

0.60.0 ≤ v < 1.0.11.1.0 ≤ v < 1.3.31.10.0 ≤ v < 1.10.21.4.0 ≤ v < 1.6.11.7.0 ≤ v < 1.9.2

Pipeline · Tektoncdgo

60%

v < 1.0.1v < 1.10.2v < 1.3.3v < 1.6.1v < 1.9.2

Affected range stops below 1.0.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.10.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.3.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.6.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 1.9.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

x_refsource_CONFIRMPatchVendor Advisory

Source: cverecord

https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj

x_refsource_MISCPatch

Source: cverecord

https://github.com/tektoncd/pipeline/commit/5eead3f859b9f938e86039e4d29185092c1d4ee6

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.5MEDIUMGitHub_M

Attack Vector: NETWORK
Complexity: LOW
Privileges: LOW
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: NONE
Availability: HIGH

Vector?

Quick Info

StatusANALYZED

CWE

CWE-129

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card