tektoncd pipeline up to 1.0.0/1.3.2/1.6.0/1.9.1/1.10.1 pathInRepo path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in tektoncd pipeline up to 1.0.0/1.3.2/1.6.0/1.9.1/1.10.1 and classified as critical. Affected by this vulnerability is an unknown functionality. Executing a manipulation of the argument pathInRepo can lead to path traversal. The identification of this vulnerability is CVE-2026-33211. The attack may be launched remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical was found in tektoncd pipeline up to 1.0.0/1.3.2/1.6.0/1.9.1/1.10.1. This vulnerability affects an unknown code. The manipulation of the argument pathInRepo with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability was named CVE-2026-33211 since 03/18/2026. The exploitation appears to be easy. The attack can be initiated remotely. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1006 by the MITRE ATT&CK project.
Upgrading to version 1.0.1, 1.3.3, 1.6.1, 1.9.2 or 1.10.2 eliminates this vulnerability. Applying the patch 10fa538f9a2b6d01c75138f1ed7ba3da0e34687c is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.6
NVD Vector: 🔒
CNA Base Score: 9.6
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Path traversalCWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: pipeline 1.0.1/1.3.3/1.6.1/1.9.2/1.10.2
Patch: 10fa538f9a2b6d01c75138f1ed7ba3da0e34687c
Timeline
03/18/2026 CVE reserved03/24/2026 Advisory disclosed
03/24/2026 VulDB entry created
03/28/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-j5q5-j9gm-2w5c
Status: Confirmed
CVE: CVE-2026-33211 (🔒)
GCVE (CVE): GCVE-0-2026-33211
GCVE (VulDB): GCVE-100-352594
Entry
Created: 03/24/2026 02:31Updated: 03/28/2026 08:29
Changes: 03/24/2026 02:31 (67), 03/28/2026 08:29 (12)
Complete: 🔍
Cache ID: 216:B37:103
No comments yet. Languages: en.
Please log in to comment.