Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5

Tekton Pipelines controller panic via long resolver name in TaskRun/PipelineRun

CVE-2026-33022GHSA-cv4x-93xx-wgfj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/tektoncd/pipeline 1.10.2, 1.9.2, 1.6.1, 1.3.3, 1.0.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/tektoncd/pipeline

    Affected
    >= 0.60.0, < 1.0.1>= 1.1.0, < 1.3.3>= 1.4.0, < 1.6.1>= 1.7.0, < 1.9.2>= 1.10.0, < 1.10.2
    Fixed in
    1.6.1, 1.9.2, 1.3.3, 1.0.1, 1.10.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-33022: 0.38% estimated exploitation activity in the next 30 days; percentile 31.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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: 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-cv4x-93xx-wgfj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-33022

Advisory: Tekton Pipelines controller panic via long resolver name in TaskRun/PipelineRun
IDs: CVE-2026-33022, GHSA-cv4x-93xx-wgfj
Record: https://patchnext.com/advisories/cve-2026-33022 (revision 1, source checked 26 Oct 2026, 15:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/tektoncd/pipeline 1.10.2, 1.9.2, 1.6.1, 1.3.3, 1.0.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/tektoncd/pipeline: affected >= 0.60.0, < 1.0.1; >= 1.1.0, < 1.3.3; >= 1.4.0, < 1.6.1; >= 1.7.0, < 1.9.2; >= 1.10.0, < 1.10.2; fixed in 1.6.1, 1.9.2, 1.3.3, 1.0.1, 1.10.2

## Suggested inspection (read-only)
- Go github.com/tektoncd/pipeline: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/tektoncd/pipeline.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cv4x-93xx-wgfj (GitHub-reviewed advisory GHSA-cv4x-93xx-wgfj lists affected ranges: Go github.com/tektoncd/pipeline >=0.60.0 =1.1.0 =1.4.0 =1.7.0 =1.10.0 <1.10.2)

Commands are suggestions: review each one before running it.

Loading voting…