CVE-2026-33211 is a critical (CVSS 9.6) path traversal in the Tekton Pipelines git resolver. A tenant who can create ResolutionRequests can read arbitrary files from the resolver pod, including ServiceAccount tokens, through the pathInRepo parameter. Upgrade to 1.0.1, 1.3.3, 1.6.1, 1.9.2 or 1.10.2.
What's affected
Tekton Pipelines starting at 1.0.0 and before the patched releases 1.0.1, 1.3.3, 1.6.1, 1.9.2 and 1.10.2. Use the fixed release on your minor line.
Exposure needs a low privilege account: anyone allowed to create ResolutionRequests, for example by creating TaskRuns or PipelineRuns that use the git resolver. Shared clusters with several tenants are the main concern.
How to check if you're exposed
Find the installed Pipelines version:
tkn version
kubectl get deploy -n tekton-pipelines -o wide
The second command shows the controller images and their tags. Then check whether the git resolver is enabled in your install and which users or service accounts can create TaskRuns, PipelineRuns or ResolutionRequests in each namespace.
Paste your lockfile into the free in-browser dependency scan to see which versions you resolve, including transitive ones. Gold also lists this CVE on its directory page.
What to do now
- Upgrade Tekton Pipelines to 1.0.1, 1.3.3, 1.6.1, 1.9.2 or 1.10.2, matching your minor line.
- Restrict who can create TaskRuns, PipelineRuns and ResolutionRequests to trusted users.
- Rotate ServiceAccount tokens that the resolver pod could read, if untrusted tenants had access.
- Review the Tekton ResolutionRequests you hold for unusual pathInRepo values.
Why it matters
The weakness class is CWE-22, path traversal. The pathInRepo value was meant to point inside a cloned repository, but it could be steered outside it and onto the resolver pod's own filesystem. The record says file contents come back base64 encoded in the status data of the resolution request, so the tenant sees them directly.
A ServiceAccount token is a credential, and the scope change in the vector reflects that reading it can reach beyond the resolver. In a CI system that credential may be powerful. The record does not flag this CVE as known exploited.
Quick check
Does this need a cluster admin account?
No. The record says a tenant with permission to create ResolutionRequests is enough, which includes creating TaskRuns or PipelineRuns that use the git resolver.
Sources
Last reviewed: 19 October 2026.
