CVE-2026-33211

CRITICALNVD 9.69.6
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
9.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.6Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.6
EG Score
9.6(low)
EPSS
43.2%
KEV
Not listed

Published

March 24, 2026

Last Modified

June 30, 2026

Advisory Details (10)

Auto-updated Jun 30, 2026
Patch available. Sources: github_commit, github, redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:10066
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:10026
github Patch Available

Path traversal in Tekton Pipelines git resolver allows reading arbitrary files from the resolver pod · Advisory · tektoncd/pipeline · GitHub

Affected: 1.0.x, 1.3.x, 1.6.x, 1.9.x, 1.10.x.

https://github.com/tektoncd/pipeline/security/advisories/GHSA-j5q5-j9gm-2w5c
github_commit

commit ec7755031a18 (tektoncd/pipeline)

Fix landed in tektoncd/pipeline commit ec7755031a18 — awaiting tagged release

https://github.com/tektoncd/pipeline/commit/ec7755031a183b345cf9e64bea0e0505c1b9cb78
github_commit

commit cdb4e1e97a4f (tektoncd/pipeline)

Fix landed in tektoncd/pipeline commit cdb4e1e97a4f — awaiting tagged release

https://github.com/tektoncd/pipeline/commit/cdb4e1e97a4f3170f9bc2cbfff83a6c8107bc3db
github_commit

commit b1fee65b88aa (tektoncd/pipeline)

Fix landed in tektoncd/pipeline commit b1fee65b88aa — awaiting tagged release

https://github.com/tektoncd/pipeline/commit/b1fee65b88aa969069c14c120045e97c37d9ee5e
github_commit

commit 961388fcf337 (tektoncd/pipeline)

Fix landed in tektoncd/pipeline commit 961388fcf337 — awaiting tagged release

https://github.com/tektoncd/pipeline/commit/961388fcf3374bc7656d28ab58ca84987e0a75ae
github_commit

commit 3ca7bc6e6dd1 (tektoncd/pipeline)

Fix landed in tektoncd/pipeline commit 3ca7bc6e6dd1 — awaiting tagged release

https://github.com/tektoncd/pipeline/commit/3ca7bc6e6dd1d97f80b84f78370d91edaf023cbd
github_commit

commit 318006c4e3a5 (tektoncd/pipeline)

Fix landed in tektoncd/pipeline commit 318006c4e3a5 — awaiting tagged release

https://github.com/tektoncd/pipeline/commit/318006c4e3a5
github_commit

commit 10fa538f9a2b (tektoncd/pipeline)

Fix landed in tektoncd/pipeline commit 10fa538f9a2b — awaiting tagged release

https://github.com/tektoncd/pipeline/commit/10fa538f9a2b6d01c75138f1ed7ba3da0e34687c

Vendor Advisories for CVE-2026-33211(12)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatserve-tkn-cli-1-21-serve-tkn-cli-1.21.12026-06-08redhat
redhatopenshift-pipelines/pipelines-pipelines-as-code-controller-rhel9:17798650012026-05-29redhat
redhatopenshift-pipelines/pipelines-operator-bundle:17800449552026-05-29redhat
redhatopenshift-builds/openshift-builds-rhel9-operator:17768602412026-04-28redhat
redhatopenshift-builds/openshift-builds-rhel9-operator:17768598982026-04-28redhat
redhatopenshift-pipelines/pipelines-resolvers-rhel9:17745966172026-04-23redhat
redhatrhtas/client-server-rhel9:17763390992026-04-23redhat
redhatopenshift-pipelines/pipelines-operator-bundle:17769251112026-04-23redhat
redhatopenshift-pipelines/pipelines-resolvers-rhel9:17745562802026-03-30redhat
redhatopenshift-pipelines/pipelines-operator-bundle:17748713902026-03-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/tektoncd/pipeline—1.0.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 11× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 04:38 UTCEG score recompute
  10. 2026-06-30 04:38 UTCVendor advisory
  11. 2026-06-30 04:32 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-33211?
CVE-2026-33211 is a critical vulnerability published on March 24, 2026. 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…
When was CVE-2026-33211 disclosed?
CVE-2026-33211 was first published in the National Vulnerability Database on March 24, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33211 actively exploited?
CVE-2026-33211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 43.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33211?
CVE-2026-33211 has a CVSS v3 base score of 9.6 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-33211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33211, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33211

Explore →

Is Your Infrastructure Affected by CVE-2026-33211?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs