CVE-2026-40938

HIGHNVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 48% 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 — 4 sources updated this weekElevated
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.5Exploit: Elevated riskExposed: 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.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1, the git resolver's revision parameter is passed directly as a positional argument to git fetch without any validation that it does not begin with a - character. Because git parses flags from mixed positional arguments, an attacker can inject arbitrary git fetch flags such as --upload-pack=. Combined with the validateRepoURL function explicitly permitting URLs that begin with / (local filesystem paths), a tenant who can submit ResolutionRequest objects can chain these two behaviors to execute an arbitrary binary on the resolver pod. The tekton-pipelines-resolvers ServiceAccount holds cluster-wide get/list/watch on all Secrets, so code execution on the resolver pod enables full cluster-wide secret exfiltration. Versions 1.0.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1 fix the issue.

CVSS v3
8.5
EG Score
8.5(medium)
EG Risk
54(Track*)
EG Risk 54/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
Severity85% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

April 21, 2026

Last Modified

July 27, 2026

Advisory Details (2)

Auto-updated Jun 9, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available

Git Resolver Unsanitized Revision Parameter Enables git Argument Injection Leading to RCE · Advisory · tektoncd/pipeline · GitHub

https://github.com/tektoncd/pipeline/security/advisories/GHSA-94jr-7pqp-xhcq
github_release Patch Available

Tekton Pipeline release v1.11.1 "Javanese Jocasta"

Patch available: tektoncd/pipeline v1.11.1

https://github.com/tektoncd/pipeline/releases/tag/v1.11.1

Vendor Advisories for CVE-2026-40938(6)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift-pipelines/pipelines-operator-bundle:17816864942026-06-17redhat
redhatopenshift-pipelines/pipelines-rhel9-operator:17806450122026-06-17redhat
redhatopenshift-builds/openshift-builds-webhook-rhel9:17803740842026-06-08redhat
redhatserve-tkn-cli-1-21-serve-tkn-cli-1.21.12026-06-08redhat
redhatopenshift-builds/openshift-builds-webhook-rhel9:17786829202026-05-14redhat

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 13× in last 7d / 45× 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 126 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-40938?
CVE-2026-40938 is a high vulnerability published on April 21, 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.2, 1.3.4, 1.6.2, 1.9.3, and 1.11.1, the git resolver's revision parameter is passed directly as a positional argument to git fetch without any validation…
When was CVE-2026-40938 disclosed?
CVE-2026-40938 was first published in the National Vulnerability Database on April 21, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40938 actively exploited?
CVE-2026-40938 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 47.6% of all scored CVEs.
What is the CVSS score of CVE-2026-40938?
CVE-2026-40938 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-40938?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40938, 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-40938

Explore →

Is Your Infrastructure Affected by CVE-2026-40938?

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

Start Free Scan →Browse All CVEs