CVE-2026-33022: Github.com/tektoncd/pipeline Tekton Pipelines Controller Panic Vulnerability

MODERATE
Advisory Identifier: GHSA-cv4x-93xx-wgfj
CVSS 6.5
CWE-400 CWE-129
Published
Advisory Summary

CVE-2026-33022 is a MODERATE (CVSS 6.5) tekton pipelines controller panic vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Github.com/tektoncd/pipeline libraries in the Go ecosystem. The issue involves tekton pipelines controller panic via long resolver name in taskrun/pipelinerun. Remediation is available by upgrading affected packages to version 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2.

CVE-2026-33022 at a Glance

CVE Identifier CVE-2026-33022
GHSA Identifier GHSA-cv4x-93xx-wgfj
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product Github.com/tektoncd/pipeline
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-33022

To remediate this vulnerability, upgrade all affected Github.com/tektoncd/pipeline dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/tektoncd/pipeline fixed: 1.0.1
Upgrade github.com/tektoncd/pipeline to 1.0.1
github.com/tektoncd/pipeline fixed: 1.3.3
Upgrade github.com/tektoncd/pipeline to 1.3.3
github.com/tektoncd/pipeline fixed: 1.6.1
Upgrade github.com/tektoncd/pipeline to 1.6.1
github.com/tektoncd/pipeline fixed: 1.9.2
Upgrade github.com/tektoncd/pipeline to 1.9.2
github.com/tektoncd/pipeline fixed: 1.10.2
Upgrade github.com/tektoncd/pipeline to 1.10.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/tektoncd/pipeline

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-33022, inspect your project dependencies for Github.com/tektoncd/pipeline:

inspect dependencies for github.com/tektoncd/pipeline

Analyze the terminal output to locate any version of Github.com/tektoncd/pipeline in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Github.com/tektoncd/pipeline, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A user with permission to create or update a TaskRun or PipelineRun can crash the Tekton Pipelines controller by setting `.spec.taskRef.resolver` (or `.spec.pipelineRef.resolver`) to a string of 31 characters or more, causing a denial of service for all reconciliation. ### Details The controller panics in `GenerateDeterministicNameFromSpec` when building a deterministic `ResolutionRequest` name. The generated name has the format `{resolver}-{hash}` and, when the resolver name is long enough, the result exceeds the DNS-1123 label limit of 63 characters. The truncation logic attempts to find a word boundary using `strings.LastIndex(name, " ")`. Since the generated name never contains spaces (it is composed of the resolver name, a dash, and a hex-encoded hash), `LastIndex` returns `-1`, which is then used as a slice bound: ```go return name[:strings.LastIndex(name[:maxLength], " ")], nil // strings.LastIndex returns -1 → panic: slice bounds out of range [:-1] ``` The panic crashes the controller. Because the offending TaskRun or PipelineRun is re-reconciled on restart, the controller enters a `CrashLoopBackOff`, blocking all TaskRun and PipelineRun reconciliation cluster-wide until the offending resource is manually deleted. Built-in resolvers use short names (`git`, `cluster`, `bundles`, `hub`) and are not affected under normal usage. The vulnerability is exploitable by any user who can create TaskRuns or PipelineRuns with a custom resolver name. ### Impact **Denial of service** — A single malicious TaskRun or PipelineRun with a long resolver name is sufficient to crash the Tekton Pipelines controller into a restart loop, blocking all CI/CD reconciliation cluster-wide until the resource is removed. ### Patches Fixed in versions 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2. The fix computes the hash first, then truncates only the prefix (resolver name) to fit within the DNS-1123 label limit, preserving the full hash to maintain determinism and uniqueness of `ResolutionRequest` names. ### Workarounds Restrict who can create TaskRun and PipelineRun resources via Kubernetes RBAC. There is no validation-side workaround without patching. ### Affected Versions All releases from **v0.60.0** through **v1.10.0**. The vulnerable truncation logic was introduced in commit `ea1fa7ad1fdc` ("Remote Resolution Refactor"), first released in v0.60.0 (2024-05-22). Currently supported affected releases: - **v1.10.x** (latest) - **v1.9.x** (LTS, EOL 2027-01-30) - **v1.6.x** (LTS, EOL 2026-10-31) - **v1.3.x** (LTS, EOL 2026-08-04) - **v1.0.x** (LTS, EOL 2026-04-29) Releases prior to v0.60.0 are **not affected** — the truncation code did not exist. ### Acknowledgments This vulnerability was reported by Oleh Konko (@1seal), who provided a thorough vulnerability analysis, proof-of-concept, and review of the fix. Thank you! ### References - Fix (main): [5eead3f859b9](https://github.com/tektoncd/pipeline/commit/5eead3f859b9f938e86039e4d29185092c1d4ee6) - Fix (v1.10.x): [01673237c464](https://github.com/tektoncd/pipeline/commit/01673237c464cfac7e286183f5c9e9d6ec951a64) - Fix (v1.9.x): [edc64bbf2232](https://github.com/tektoncd/pipeline/commit/edc64bbf22323fcf218170f19047c9bcd8163e90) - Fix (v1.6.x): [0fa2d66cff81](https://github.com/tektoncd/pipeline/commit/0fa2d66cff814838c3a10cce252104c7fe618932) - Fix (v1.3.x): [5e4905fb6754](https://github.com/tektoncd/pipeline/commit/5e4905fb6754efa5ecea54de195738d73fb0e01d) - Fix (v1.0.x): [ebc197e2b973](https://github.com/tektoncd/pipeline/commit/ebc197e2b9733deedaa1624212ec66dcdf61eaaf) - Introduced in: `ea1fa7ad1fdc` ("Remote Resolution Refactor")

CVE-2026-33022 Affected Github.com/tektoncd/pipeline Versions

5 component(s)
Fixed Versions:
1.0.11.3.31.6.11.9.21.10.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/tektoncd/pipeline
Go
≥ 0.60.0
< 1.0.1
1.0.1
github.com/tektoncd/pipeline
Go
≥ 1.1.0
< 1.3.3
1.3.3
github.com/tektoncd/pipeline
Go
≥ 1.4.0
< 1.6.1
1.6.1
github.com/tektoncd/pipeline
Go
≥ 1.7.0
< 1.9.2
1.9.2
github.com/tektoncd/pipeline
Go
≥ 1.10.0
< 1.10.2
1.10.2

References

Frequently Asked Questions

What is CVE-2026-33022?
CVE-2026-33022 is a security vulnerability in Github.com/tektoncd/pipeline involving Tekton Pipelines controller panic via long resolver name in TaskRun/PipelineRun under CWE-400: Uncontrolled Resource Consumption.
Which Github.com/tektoncd/pipeline versions are affected?
Affected versions include releases prior to 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2 across affected packages: github.com/tektoncd/pipeline.
What version fixes CVE-2026-33022?
Upgrading to 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/tektoncd/pipeline affected?
Yes, github.com/tektoncd/pipeline is affected in releases prior to 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2. Upgrade your dependency to 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2 or later.
What is the CVSS score of CVE-2026-33022?
CVE-2026-33022 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-33022?
CVE-2026-33022 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check Go dependencies for CVE-2026-33022?
Run the dependency tree command: 'inspect dependencies for github.com/tektoncd/pipeline'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-cv4x-93xx-wgfj",
  "modified" : "2026-03-25T18:26:47Z",
  "published" : "2026-03-17T19:46:29Z",
  "aliases" : [ "CVE-2026-33022" ],
  "summary" : "Tekton Pipelines controller panic via long resolver name in TaskRun/PipelineRun",
  "details" : "### Summary\n\nA user with permission to create or update a TaskRun or PipelineRun can crash the Tekton Pipelines controller by setting `.spec.taskRef.resolver` (or `.spec.pipelineRef.resolver`) to a string of 31 characters or more, causing a denial of service for all reconciliation.\n\n### Details\n\nThe controller panics in `GenerateDeterministicNameFromSpec` when building a deterministic `ResolutionRequest` name. The generated name has the format `{resolver}-{hash}` and, when the resolver name is long enough, the result exceeds the DNS-1123 label limit of 63 characters.\n\nThe truncation logic attempts to find a word boundary using `strings.LastIndex(name, \" \")`. Since the generated name never contains spaces (it is composed of the resolver name, a dash, and a hex-encoded hash), `LastIndex` returns `-1`, which is then used as a slice bound:\n\n```go\nreturn name[:strings.LastIndex(name[:maxLength], \" \")], nil\n// strings.LastIndex returns -1 → panic: slice bounds out of range [:-1]\n```\n\nThe panic crashes the controller. Because the offending TaskRun or PipelineRun is re-reconciled on restart, the controller enters a `CrashLoopBackOff`, blocking all TaskRun and PipelineRun reconciliation cluster-wide until the offending resource is manually deleted.\n\nBuilt-in resolvers use short names (`git`, `cluster`, `bundles`, `hub`) and are not affected under normal usage. The vulnerability is exploitable by any user who can create TaskRuns or PipelineRuns with a custom resolver name.\n\n### Impact\n\n**Denial of service** — A single malicious TaskRun or PipelineRun with a long resolver name is sufficient to crash the Tekton Pipelines controller into a restart loop, blocking all CI/CD reconciliation cluster-wide until the resource is removed.\n\n### Patches\n\nFixed in versions 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2.\n\nThe fix computes the hash first, then truncates only the prefix (resolver name) to fit within the DNS-1123 label limit, preserving the full hash to maintain determinism and uniqueness of `ResolutionRequest` names.\n\n### Workarounds\n\nRestrict who can create TaskRun and PipelineRun resources via Kubernetes RBAC. There is no validation-side workaround without patching.\n\n### Affected Versions\n\nAll releases from **v0.60.0** through **v1.10.0**.\n\nThe vulnerable truncation logic was introduced in commit `ea1fa7ad1fdc` (\"Remote Resolution Refactor\"), first released in v0.60.0 (2024-05-22).\n\nCurrently supported affected releases:\n- **v1.10.x** (latest)\n- **v1.9.x** (LTS, EOL 2027-01-30)\n- **v1.6.x** (LTS, EOL 2026-10-31)\n- **v1.3.x** (LTS, EOL 2026-08-04)\n- **v1.0.x** (LTS, EOL 2026-04-29)\n\nReleases prior to v0.60.0 are **not affected** — the truncation code did not exist.\n\n### Acknowledgments\n\nThis vulnerability was reported by Oleh Konko (@1seal), who provided a thorough vulnerability analysis, proof-of-concept, and review of the fix. Thank you!\n\n### References\n\n- Fix (main): [5eead3f859b9](https://github.com/tektoncd/pipeline/commit/5eead3f859b9f938e86039e4d29185092c1d4ee6)\n- Fix (v1.10.x): [01673237c464](https://github.com/tektoncd/pipeline/commit/01673237c464cfac7e286183f5c9e9d6ec951a64)\n- Fix (v1.9.x): [edc64bbf2232](https://github.com/tektoncd/pipeline/commit/edc64bbf22323fcf218170f19047c9bcd8163e90)\n- Fix (v1.6.x): [0fa2d66cff81](https://github.com/tektoncd/pipeline/commit/0fa2d66cff814838c3a10cce252104c7fe618932)\n- Fix (v1.3.x): [5e4905fb6754](https://github.com/tektoncd/pipeline/commit/5e4905fb6754efa5ecea54de195738d73fb0e01d)\n- Fix (v1.0.x): [ebc197e2b973](https://github.com/tektoncd/pipeline/commit/ebc197e2b9733deedaa1624212ec66dcdf61eaaf)\n- Introduced in: `ea1fa7ad1fdc` (\"Remote Resolution Refactor\")",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/tektoncd/pipeline"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.60.0"
      }, {
        "fixed" : "1.0.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/tektoncd/pipeline"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.1.0"
      }, {
        "fixed" : "1.3.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/tektoncd/pipeline"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.4.0"
      }, {
        "fixed" : "1.6.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/tektoncd/pipeline"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.7.0"
      }, {
        "fixed" : "1.9.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/tektoncd/pipeline"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.10.0"
      }, {
        "fixed" : "1.10.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33022"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tektoncd/pipeline/commit/01673237c464cfac7e286183f5c9e9d6ec951a64"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tektoncd/pipeline/commit/0fa2d66cff814838c3a10cce252104c7fe618932"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tektoncd/pipeline/commit/5e4905fb6754efa5ecea54de195738d73fb0e01d"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tektoncd/pipeline/commit/5eead3f859b9f938e86039e4d29185092c1d4ee6"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tektoncd/pipeline/commit/ebc197e2b9733deedaa1624212ec66dcdf61eaaf"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tektoncd/pipeline/commit/edc64bbf22323fcf218170f19047c9bcd8163e90"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/tektoncd/pipeline"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-129", "CWE-400" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-17T19:46:29Z",
    "nvd_published_at" : "2026-03-20T08:16:11Z"
  }
}