Skip to content
Connect AISign inSign up free
CVE-2026-332119.6CriticalCWE-22

CVE-2026-33211: Tekton Pipelines git resolver has path traversal that allows reading arbitrary files from the resolver pod

tektoncd · pipeline

Vendor fix available · Affected: tektoncd pipeline · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.6%probability of exploitation in the next 30 days
49th percentile
050100

Higher than 49% of scored CVEs

9.6CriticalCVSS 3.1
LowCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • tektoncd · pipeline>= 1.0.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

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
tektoncd
Published
March 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-33211 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

9 more references are in the CVE record.