dbcve.org
Tekton PipelinesApplication · Linuxfoundation

CVE-2026-33211

CRITICAL · 9.6 CVSS v3.1 Published 2026-03-24
Fix available
A fix is available. Upgrade to 1.3.3 / 1.6.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines. Starting in version 1.0.0 and prior to versions 1.0.1, 1.3.3, 1.6.1, 1.9.2, and 1.10.2, the Tekton Pipelines git resolver is vulnerable to path traversal via the `pathInRepo` parameter. A tenant with permission to create `ResolutionRequests` (e.g. by creating `TaskRuns` or `PipelineRuns` that use the git resolver) can read arbitrary files from the resolver pod's filesystem, including ServiceAccount tokens. The file contents are returned base64-encoded in `resolutionrequest.status.data`. Versions 1.0.1, 1.3.3, 1.6.1, 1.9.2, and 1.10.2 contain a patch.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Tekton Pipelines git resolver has a path traversal vulnerability in the pathInRepo parameter. An authenticated tenant with permission to create ResolutionRequests (via TaskRuns or PipelineRuns using the git resolver) can read arbitrary files from the resolver pod's filesystem, including ServiceAccount tokens, with contents returned base64-encoded in resolutionrequest.status.data.

MitigationUpgrade Tekton Pipelines to versions 1.0.1, 1.3.3, 1.6.1, 1.9.2, or 1.10.2 or later. Until patched, strictly limit who can create ResolutionRequests and consider network policies to restrict resolver pod access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tekton PipelinesApplication
Affected:>= 1.1.0, < 1.3.3>= 1.4.0, < 1.6.1>= 1.7.0, < 1.9.2>= 1.10.0, < 1.10.2= 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Tekton Pipelines version
    Run 'kubectl get tektonpipelines -n tekton-pipelines tekton-pipelines -o jsonpath={.spec.version}' or check the installed Tekton Pipelines operator version
    Affected if The installed version matches any of the affected ranges: 1.0.0, 1.1.0 to <1.3.3, 1.4.0 to <1.6.1, 1.7.0 to <1.9.2, or 1.10.0 to <1.10.2
  2. Confirm git resolver is in use
    Query for ResolutionRequests with spec.resolver set to 'git': kubectl get resolutionrequests -A -o json | jq '.items[] | select(.spec.resolver=="git")'
    Affected if Any ResolutionRequests exist with the git resolver, indicating the vulnerable component is active
  3. Review ResolutionRequests for suspicious pathInRepo values
    Examine ResolutionRequest objects for pathInRepo values containing '../' or absolute paths like '/etc/secrets' or '/var/run/secrets': kubectl get resolutionrequests -A -o json | jq '.items[] | select(.spec.params.pathInRepo | test("^/|\.\./"))'
    Affected if ResolutionRequests contain pathInRepo values starting with '/' or containing '../', indicating potential exploitation attempts
  4. Inspect ResolutionRequest status for unexpected base64 data
    Check resolutionrequest.status.data for base64-encoded content from unexpected files: kubectl get resolutionrequests -A -o json | jq '.items[] | .status.data' | base64 -d (where applicable)
    Affected if ResolutionRequest status data decodes to contents from files outside the expected repository, such as /etc/passwd or secret token files

You are affected if Tekton Pipelines version is 1.0.0 or within 1.1.0-<1.3.3, 1.4.0-<1.6.1, 1.7.0-<1.9.2, or 1.10.0-<1.10.2 AND the git resolver is being used to create ResolutionRequests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.3.3 / 1.6.1 / 1.9.2 or later
Fixed in 1.3.31.6.11.9.2
Vendor patch github.com →
Interim mitigation

Upgrade Tekton Pipelines to versions 1.0.1, 1.3.3, 1.6.1, 1.9.2, or 1.10.2 or later. Until patched, strictly limit who can create ResolutionRequests and consider network policies to restrict resolver pod access.

Recommended fix High confidence

Upgrade to Tekton Pipelines version 1.10.2 or later (e.g., 1.10.2, 1.11.0, or latest stable)

  1. 1. Identify the current Tekton Pipelines version running in your cluster using: kubectl get tektonconfig -o yaml
  2. 2. Check which PipelineRuns or TaskRuns are using the git resolver by looking for resources with spec.resolution: git or resolutionRequest annotations
  3. 3. Upgrade Tekton Pipelines to version 1.10.2 or later by applying the latest Tekton Operator manifest, or running: kubectl apply -f https://storage.googleapis.com/tekton-releases/pipeline/previous/v1.10.2/release.yaml
  4. 4. Verify the upgrade was successful: kubectl get tektonconfig -o yaml and confirm the version shows 1.10.2
  5. 5. Test that the git resolver still functions correctly with a sample TaskRun using the git resolver
  6. 6. Review any PipelineRuns or TaskRuns that may have been exploiting this vulnerability to determine if tokens were exfiltrated
Caveat Minor: This is a security patch with minimal expected breaking changes; however, test in staging first as with any upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tekton Pipelines Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33211 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33211 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data