Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NSummary
CVE-2026-33211 is a critical-severity Path Traversal (CWE-22) vulnerability in Linuxfoundation Tekton Pipelines. Its CVSS base score is 9.6 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 44th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33211 is a path traversal vulnerability (CWE-22) in the Tekton Pipelines git resolver, which provides Kubernetes-style resources for declaring CI/CD pipelines. The issue affects versions starting from 1.0.0 and prior to the patched releases 1.0.1, 1.3.3, 1.6.1, 1.9.2, and 1.10.2. Exploitation occurs via the `pathInRepo` parameter, allowing unauthorized access to files outside the intended repository path.
A tenant with permissions to create `ResolutionRequests`—typically gained by initiating `TaskRuns` or `PipelineRuns` that leverage the git resolver—can exploit this flaw. Attackers achieve arbitrary file reads from the resolver pod's filesystem, including sensitive items like ServiceAccount tokens. Retrieved file contents are returned base64-encoded in the `resolutionrequest.status.data` field. The vulnerability carries a CVSS v3.1 base score of 9.6 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N), reflecting its network reach, low attack complexity, low privileges required, and potential for high confidentiality and integrity impacts across a scoped network.
Patched versions 1.0.1, 1.3.3, 1.6.1, 1.9.2, and 1.10.2 address the issue, as implemented in the following Tekton Pipelines GitHub commits: 10fa538f9a2b6d01c75138f1ed7ba3da0e34687c, 318006c4e3a5, 3ca7bc6e6dd1d97f80b84f78370d91edaf023cbd, 961388fcf3374bc7656d28ab58ca84987e0a75ae, and b1fee65b88aa969069c14c120045e97c37d9ee5e. Security practitioners should upgrade to these versions and review access controls for `ResolutionRequests` in multi-tenant Kubernetes environments.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-14636
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Input validation directly neutralizes special path elements before pathname construction occurs.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches path traversal via static/dynamic analysis.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.
Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.
Information access restriction limits which files an application may read or write.