CVE-2026-33022: Tekton Pipelines: Controller can panic when setting long resolver names in TaskRun/PipelineRun

Severity: medium (CVSS 6.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.4% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-03-20 · updated 2026-06-17
Weakness: CWE-129

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 products

tektoncd pipeline: from 0.60.0 before 1.0.1; from 1.1.0 before 1.3.3; from 1.4.0 before 1.6.1; from 1.7.0 before 1.9.2; from 1.10.0 before 1.10.2 — fixed in 1.0.1, 1.10.2, 1.3.3, 1.6.1, 1.9.2

How to fix

Upgrade to a fixed version: tektoncd pipeline 1.0.1, 1.10.2, 1.3.3, 1.6.1. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-33022 or the next vulnerability affects your stack