CVE-2026-40938

HIGHNVD 8.58.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.5 under NVD CVSS v3. EPSS exploit probability: 0.9% (59th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekElevated
8.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.5Exploit: No code on recordExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 21, 2026

Last Modified

September 7, 2026

Advisory Details (2)

Auto-updated Jun 9, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

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

Patch Availability(5)

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 rangeFix by version rangeDependents
github.com/tektoncd/pipeline—
  • 1.10.0 up to 1.11.1: fixed in 1.11.1
  • 1.7.0 up to 1.9.3: fixed in 1.9.3
  • 1.4.0 up to 1.6.2: fixed in 1.6.2
  • 1.2.0 up to 1.3.4: fixed in 1.3.4
  • 1.0.0 up to 1.0.2: fixed in 1.0.2
  • 1.1.0 up to 1.3.4: fixed in 1.3.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 248 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 148 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-40938?
CVE-2026-40938 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-40938 published?
The CVE record for CVE-2026-40938 was published on April 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 7, 2026; the record at its source may have been updated since.
Is CVE-2026-40938 actively exploited?
CVE-2026-40938 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-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?
A fix for CVE-2026-40938 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-40938 are linked in the Vendor Advisories panel on this page.

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.