# CVE-2026-33022: Tekton Pipelines: Controller can panic when setting long resolver names in TaskRun/PipelineRun > An attacker can crash the Tekton controller by creating a TaskRun with a long custom resolver name, blocking all CI/CD operations. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Mar 2026 - **Updated:** 20 Mar 2026 - **Also known as:** CLEANSTART-2026-FN18256, GHSA-cv4x-93xx-wgfj, GO-2026-4730 ## What is CVE-2026-33022? CVE-2026-33022 is a medium-severity denial of service vulnerability in tektoncd pipeline, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-129 (Improper Validation of Array Index) ## Which versions are affected by CVE-2026-33022? 11 open source packages ship an affected version, including github.com/tektoncd/pipeline. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/tektoncd/pipeline` | Go | From 0.60.0 | 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2 | | `github.com/tektoncd/pipeline` | Go | From 0.60.0 | 1.0.1 | | `github.com/tektoncd/pipeline` | Go | From 0.60.0 | 1.0.1 | | `github.com/tektoncd/pipeline` | Go | From 1.1.0 | 1.3.3 | | `github.com/tektoncd/pipeline` | Go | From 1.1.0 | 1.3.3 | | `github.com/tektoncd/pipeline` | Go | From 1.10.0 | 1.10.2 | | `github.com/tektoncd/pipeline` | Go | From 1.10.0 | 1.10.2 | | `github.com/tektoncd/pipeline` | Go | From 1.4.0 | 1.6.1 | | `github.com/tektoncd/pipeline` | Go | From 1.4.0 | 1.6.1 | | `github.com/tektoncd/pipeline` | Go | From 1.7.0 | 1.9.2 | | `github.com/tektoncd/pipeline` | Go | From 1.7.0 | 1.9.2 | Products: Linuxfoundation Tekton Pipelines. ## How do I fix CVE-2026-33022? Upgrade github.com/tektoncd/pipeline to a fixed version for your release line: 1.0.1, 1.3.3, 1.6.1 or 1.9.2. ## Is CVE-2026-33022 being exploited? There is no known exploitation of CVE-2026-33022 in the wild and no public exploit code. ## Other vulnerabilities in tektoncd pipeline - [CVE-2026-33211](https://insights.sbomify.com/CVE-2026-33211/): Tekton Pipelines git resolver has path traversal that allows reading arbitrary files from the resolver pod (critical 9.6) - [CVE-2026-40161](https://insights.sbomify.com/CVE-2026-40161/): Tekton Pipelines: Git resolver API mode leaks system-configured API token to user-controlled serverURL (high 7.7) - [CVE-2026-40938](https://insights.sbomify.com/CVE-2026-40938/): Tekton Pipelines: Git Resolver Unsanitized Revision Parameter Enables git Argument Injection Leading to RCE (high 7.5) - [CVE-2026-25542](https://insights.sbomify.com/CVE-2026-25542/): Tekton Pipelines: VerificationPolicy regex pattern bypass via substring matching (medium 6.5) - [CVE-2026-40924](https://insights.sbomify.com/CVE-2026-40924/): Tekton Pipelines: HTTP Resolver Unbounded Response Body Read Enables Denial of Service via Memory Exhaustion (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-33022 and fix it if it is affected. What it is: CVE-2026-33022 is a medium-severity denial of service vulnerability in tektoncd pipeline, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-33022 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/tektoncd/pipeline (Go): affected from 0.60.0; fixed in 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2 - github.com/tektoncd/pipeline (Go): affected from 0.60.0; fixed in 1.0.1 - github.com/tektoncd/pipeline (Go): affected from 0.60.0; fixed in 1.0.1 - github.com/tektoncd/pipeline (Go): affected from 1.1.0; fixed in 1.3.3 - github.com/tektoncd/pipeline (Go): affected from 1.1.0; fixed in 1.3.3 - github.com/tektoncd/pipeline (Go): affected from 1.10.0; fixed in 1.10.2 - github.com/tektoncd/pipeline (Go): affected from 1.10.0; fixed in 1.10.2 - github.com/tektoncd/pipeline (Go): affected from 1.4.0; fixed in 1.6.1 - github.com/tektoncd/pipeline (Go): affected from 1.4.0; fixed in 1.6.1 - github.com/tektoncd/pipeline (Go): affected from 1.7.0; fixed in 1.9.2 - github.com/tektoncd/pipeline (Go): affected from 1.7.0; fixed in 1.9.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-33022/ (Markdown: https://insights.sbomify.com/CVE-2026-33022/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33022 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33022 - OSV: https://osv.dev/vulnerability/CVE-2026-33022 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-33022/ Summaries are generated and may contain mistakes; the official description above is the record.