Security Digest · Vulnerability record
CVE-2026-33211: Path traversal in Tekton Pipelines git resolver allows reading arbitrary files from the resolver pod
Tekton Pipelines project provides k8s-style resources for declaring CI/CD-style pipelines.
CVSS 9.6 Critical EPSS 0.7% · p54
Should you act?
Critical, preconditions apply
Severe if exploited, but exploitation needs conditions that may not apply to you. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.7%, percentile 54: FIRST’s model estimates a 0.7% chance of exploitation activity in the next 30 days, higher than 54% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Needs an account (low (any account)). Exposure depends on who can log in.
- Only applies if your dependency tree includes
github.com/tektoncd/pipeline(Go) >= 1.0.0, < 1.0.1, fixed in 1.0.1;github.com/tektoncd/pipeline(Go) >= 1.1.0, < 1.3.3, fixed in 1.3.3;github.com/tektoncd/pipeline(Go) >= 1.4.0, < 1.6.1, fixed in 1.6.1;github.com/tektoncd/pipeline(Go) >= 1.7.0, < 1.9.2, fixed in 1.9.2. Check your lockfile, including transitive dependencies.
What it is
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.
From the GitHub advisory
Summary
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.
Details
The git resolver's getFileContent() function in pkg/resolution/resolver/git/repository.go constructs a file path by joining the repository clone directory with the user-supplied pathInRepo parameter:
The pathInRepo parameter is not validated for path traversal sequences. An attacker can supply values like ../../../../etc/passwd to escape the cloned repository directory and read arbitrary files from the resolver pod's filesystem.
Weakness type: CWE-22.
Product: github.com/tektoncd/pipeline (Go) · Assigned by: GitHub_M · Published: 2026-03-23
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| Go | github.com/tektoncd/pipeline | >= 1.0.0, < 1.0.1 | 1.0.1 |
| Go | github.com/tektoncd/pipeline | >= 1.1.0, < 1.3.3 | 1.3.3 |
| Go | github.com/tektoncd/pipeline | >= 1.4.0, < 1.6.1 | 1.6.1 |
| Go | github.com/tektoncd/pipeline | >= 1.7.0, < 1.9.2 | 1.9.2 |
| Go | github.com/tektoncd/pipeline | >= 1.10.0, < 1.10.2 | 1.10.2 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| 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 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_M | 3.1 | 9.6 Critical | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
| redhat-SADP | 3.1 | 9.6 Critical | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
| GitHub | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: low (any account)
- User interaction: none
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable no, technical impact partial.
- FIRST EPSS (model of 2026-10-21): 0.73% probability of exploitation activity in the next 30 days; percentile 54.
Timeline
- — GitHub-reviewed advisory GHSA-j5q5-j9gm-2w5c published (critical)
- — CVE record published by GitHub_M
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vendor and project advisories, patches
- access.redhat.com access.redhat.com
- access.redhat.com access.redhat.com
- access.redhat.com access.redhat.com
- access.redhat.com access.redhat.com
- access.redhat.com access.redhat.com
- access.redhat.com access.redhat.com
- access.redhat.com access.redhat.com
- access.redhat.com access.redhat.com
- access.redhat.com access.redhat.com
- access.redhat.com access.redhat.com
Vulnerability records
- GitHub Advisory GHSA-j5q5-j9gm-2w5c github.com
- CVE.org record CVE-2026-33211 cve.org
- NVD entry CVE-2026-33211 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
- access.redhat.com access.redhat.com
- RHBZ#2450554 bugzilla.redhat.com
- security.access.redhat.com security.access.redhat.com