CVE-2026-33022: GO-2026-4730 - Tekton Pipelines controller panic via long resolver name in TaskRun/PipelineRun in github.com/tektoncd/pipeline

CVE-2026-33022 · Severity: low · CVSS 3.1 · Published 2026-03-23

Tekton Pipelines controller panic via long resolver name in TaskRun/PipelineRun in github.com/tektoncd/pipeline

Technologies: github.com/tektoncd/pipeline (Go). Vendors: Go.

Quick answers

Is CVE-2026-33022 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-33022 being exploited in the wild.
How severe is CVE-2026-33022?
Low severity, with a CVSS score of 3.1, published 23 March 2026.
Which products and versions are affected?
github.com/tektoncd/pipeline (Go) SEMVER:introduced=0.60.0,fixed=1.0.1, SEMVER:introduced=0.60.0,fixed=1.0.1,introduced=1.1.0,fixed=1.3.3,introduced=1.4.0,fixed=1.6.1,introduced=1.7.0,fixed=1.9.2,introduced=1.10.0,fixed=1.10.2.
Is there a fix for CVE-2026-33022?
Yes. github.com/tektoncd/pipeline (Go): upgrade to 1.0.1, 1.10.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-33022?
Check whether you run github.com/tektoncd/pipeline (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/tektoncd/pipeline (Go): upgrade to 1.0.1, 1.10.2 or later
    go get github.com/tektoncd/pipeline@v1.10.2

Affected products

  • github.com/tektoncd/pipeline (Go) SEMVER:introduced=0.60.0,fixed=1.0.1, SEMVER:introduced=0.60.0,fixed=1.0.1,introduced=1.1.0,fixed=1.3.3,introduced=1.4.0,fixed=1.6.1,introduced=1.7.0,fixed=1.9.2,introduced=1.10.0,fixed=1.10.2

Identifiers

  • CVE-2026-33022
  • GHSA-cv4x-93xx-wgfj
  • GO-2026-4730

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.