CVE-2026-33211

CRITICALNVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 55% of all CVEs by exploit prediction. 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: epss, nvd
Trending — 3 sources updated this week
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.6Exploit: None knownExposed: 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(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity96% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

March 24, 2026

Last Modified

August 24, 2026

Advisory Details (10)

Auto-updated Aug 25, 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.11.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 86× 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.

Showing the most recent 100 of 127 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 14:17 UTCEPSS rescore
  3. 2026-08-24 13:31 UTCVendor advisory
  4. 2026-08-24 12:27 UTCEG score recompute
  5. 2026-08-24 12:27 UTCVendor advisory
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 17:03 UTCEPSS rescore
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 12:21 UTCVendor advisory
  14. 2026-08-17 12:13 UTCEG score recompute
  15. 2026-08-17 12:13 UTCVendor advisory
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 10:43 UTCEG score recompute
  18. 2026-08-16 10:43 UTCVendor advisory
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-14 23:43 UTCVendor advisory
  22. 2026-08-14 19:44 UTCVendor advisory
  23. 2026-08-14 14:51 UTCVendor advisory
  24. 2026-08-14 10:53 UTCVendor advisory
  25. 2026-08-14 06:55 UTCEG score recompute
Show 75 more
  1. 2026-08-14 06:55 UTCVendor advisory
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-13 01:35 UTCVendor advisory
  4. 2026-08-12 21:37 UTCEG score recompute
  5. 2026-08-12 21:37 UTCVendor advisory
  6. 2026-08-12 13:50 UTCEPSS rescore
  7. 2026-08-12 01:10 UTCVendor advisory
  8. 2026-08-11 21:12 UTCEG score recompute
  9. 2026-08-11 21:12 UTCVendor advisory
  10. 2026-08-11 08:29 UTCVendor advisory
  11. 2026-08-11 04:15 UTCEG score recompute
  12. 2026-08-11 04:15 UTCVendor advisory
  13. 2026-08-11 00:00 UTCEPSS rescore
  14. 2026-08-10 13:08 UTCVendor advisory
  15. 2026-08-10 09:09 UTCVendor advisory
  16. 2026-08-10 05:11 UTCVendor advisory
  17. 2026-08-10 01:13 UTCVendor advisory
  18. 2026-08-09 21:15 UTCVendor advisory
  19. 2026-08-09 17:17 UTCEG score recompute
  20. 2026-08-09 17:17 UTCVendor advisory
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-09 13:18 UTCVendor advisory
  23. 2026-08-09 06:31 UTCEG score recompute
  24. 2026-08-09 06:31 UTCVendor advisory
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-08 08:47 UTCVendor advisory
  27. 2026-08-08 04:49 UTCVendor advisory
  28. 2026-08-08 00:51 UTCVendor advisory
  29. 2026-08-07 20:51 UTCVendor advisory
  30. 2026-08-07 16:53 UTCEG score recompute
  31. 2026-08-07 16:53 UTCVendor advisory
  32. 2026-08-06 19:09 UTCEG score recompute
  33. 2026-08-06 19:09 UTCVendor advisory
  34. 2026-08-06 13:46 UTCEPSS rescore
  35. 2026-08-06 09:12 UTCVendor advisory
  36. 2026-08-06 05:13 UTCVendor advisory
  37. 2026-08-06 01:15 UTCEG score recompute
  38. 2026-08-06 01:15 UTCVendor advisory
  39. 2026-08-05 19:17 UTCEPSS rescore
  40. 2026-08-04 15:10 UTCEPSS rescore
  41. 2026-08-04 10:38 UTCEPSS rescore
  42. 2026-08-04 04:01 UTCVendor advisory
  43. 2026-08-03 23:58 UTCVendor advisory
  44. 2026-08-03 13:44 UTCVendor advisory
  45. 2026-08-03 12:49 UTCEG score recompute
  46. 2026-08-03 12:49 UTCVendor advisory
  47. 2026-08-03 10:36 UTCEPSS rescore
  48. 2026-08-02 23:48 UTCVendor advisory
  49. 2026-08-02 19:49 UTCVendor advisory
  50. 2026-08-02 15:51 UTCEG score recompute
  51. 2026-08-02 15:51 UTCVendor advisory
  52. 2026-08-02 02:27 UTCEPSS rescore
  53. 2026-08-01 04:16 UTCEPSS rescore
  54. 2026-07-30 16:28 UTCEPSS rescore
  55. 2026-07-30 01:30 UTCEPSS rescore
  56. 2026-07-28 12:33 UTCEG score recompute
  57. 2026-07-28 12:33 UTCVendor advisory
  58. 2026-07-27 14:13 UTCEPSS rescore
  59. 2026-07-27 13:31 UTCVendor advisory
  60. 2026-07-27 12:41 UTCEG score recompute
  61. 2026-07-27 12:41 UTCVendor advisory
  62. 2026-07-26 14:54 UTCEPSS rescore
  63. 2026-07-26 14:54 UTCEPSS rescore
  64. 2026-07-25 14:18 UTCEPSS rescore
  65. 2026-07-25 14:18 UTCEPSS rescore
  66. 2026-07-24 14:17 UTCEPSS rescore
  67. 2026-07-24 14:17 UTCEPSS rescore
  68. 2026-07-23 14:18 UTCEPSS rescore
  69. 2026-07-23 14:18 UTCEPSS rescore
  70. 2026-07-23 03:09 UTCEG score recompute
  71. 2026-07-22 14:08 UTCEPSS rescore
  72. 2026-07-21 15:24 UTCEPSS rescore
  73. 2026-07-20 17:08 UTCEPSS rescore
  74. 2026-07-19 14:31 UTCEPSS rescore
  75. 2026-07-19 02:29 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

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 August 24, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 55.2% of all scored CVEs.
What is the CVSS score of CVE-2026-33211?
CVE-2026-33211 has a CVSS v3 base score of 9.6 (NVD).
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