CVE-2026-54136

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-63484 (ENISA EUVD) · GHSA-2ppx-66jv-wpw5 (GitHub Security Advisories)Source: ENISA EUVD

5.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Windmill is an open-source developer platform for internal code: APIs, background jobs, workflows and UIs. Prior to 1.715.0, a resource-scoped API token could read script contents outside its allowed path scope through GET /api/w/{workspace}/scripts/list_search. The route-level scope middleware validated the token domain and action but did not enforce the resource/path segment, and the list_search_scripts handler had no additional check_scopes call or per-row filtering before returning script path and content fields. A token such as scripts:read:f/allowed/* could therefore receive source code for unrelated paths in the same workspace, potentially disclosing internal automation logic, integration details, business logic, inline configuration, or hardcoded secrets and credentials. Exploitation required possession of a valid scoped API token for the workspace but did not require administrator privileges. This issue is fixed in version 1.715.0.

CVSS v3
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
23
EG Risk 23/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)
Severity51% × 45%
Impact severity (EG Severity): CVSS 5.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.5%
EPSS %ILE
40th
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 (5.1): severity, escalated by confirmed exploitation. This CVE's 5.1 is its impact severity (EG Severity), not escalated.

EG Severity
5.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

July 10, 2026

Last Modified

October 18, 2026

Advisory Details (4)

Auto-updated Aug 20, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
GitHub release Patch Available

v1.715.0

Patch available: windmill-labs/windmill v1.715.0

https://github.com/windmill-labs/windmill/releases/tag/v1.715.0
GitHub commit

commit 7edf3f02122e (windmill-labs/windmill)

Fix landed in windmill-labs/windmill commit 7edf3f02122e — awaiting tagged release

https://github.com/windmill-labs/windmill/commit/7edf3f02122e20fde1e95e0252e7bda641075326
GitHub pull request

fix(auth): filter script/flow listings by token scope (GHSA-2ppx-66jv-wpw5)

Fix merged in windmill-labs/windmill PR #9426 on 2026-06-03 — awaiting tagged release

https://github.com/windmill-labs/windmill/pull/9426
GitHub advisoryMentions a patch (unverified)

Resource-scoped API tokens can read script contents outside their allowed path via scripts/list_search · Advisory · windmill-labs/windmill · GitHub

https://github.com/windmill-labs/windmill/security/advisories/GHSA-2ppx-66jv-wpw5

Vendor Advisories for CVE-2026-54136(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustwindmill-api @ 1.715.0 (fixes <= 1.714.1)—ghsa

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)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
windmill-api—
  • every version up to 1.715.0: fixed in 1.715.0
—

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-11-01 07:44 UTCGHSA enrichmentGHSA-2ppx-66jv-wpw5 · GitHub severity MODERATE
  3. 2026-11-01 07:44 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-29 14:43 UTCEG score recompute
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-10-28 04:25 UTCOSV refresh
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-25 14:19 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-10-18 20:36 UTCEG score recompute
  21. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  22. 2026-10-18 03:31 UTCEG score recompute
  23. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 75 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-12 15:56 UTCEG score recompute
  5. 2026-10-11 19:40 UTCEG score recompute
  6. 2026-10-11 16:55 UTCEG score recompute
  7. 2026-10-11 14:18 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  16. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-10-01 14:58 UTCEG score recompute
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-09-28 09:47 UTCEG score recompute
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  26. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  27. 2026-09-24 11:10 UTCEG score recompute
  28. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  29. 2026-09-23 05:45 UTCEG score recompute
  30. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  31. 2026-09-18 20:35 UTCEG score recompute
  32. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  33. 2026-09-18 05:18 UTCEG score recompute
  34. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  35. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  36. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  37. 2026-09-14 08:28 UTCEG score recompute
  38. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  39. 2026-09-13 08:11 UTCEG score recompute
  40. 2026-09-12 02:52 UTCEG score recompute
  41. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  42. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  43. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  44. 2026-09-08 02:48 UTCEG score recompute
  45. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  46. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  47. 2026-09-05 21:41 UTCEG score recompute
  48. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  49. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  50. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  51. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  52. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  53. 2026-08-30 06:19 UTCEG score recompute
  54. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  55. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  56. 2026-08-28 04:29 UTCEG score recompute
  57. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  58. 2026-08-27 04:01 UTCEG score recompute
  59. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  60. 2026-08-26 03:34 UTCEG score recompute
  61. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  62. 2026-08-24 23:20 UTCEG score recompute
  63. 2026-08-23 23:05 UTCEG score recompute
  64. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  65. 2026-08-22 22:42 UTCEG score recompute
  66. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  67. 2026-08-21 22:27 UTCEG score recompute
  68. 2026-08-21 22:01 UTCEG score recompute
  69. 2026-08-20 17:35 UTCEG score recompute
  70. 2026-08-20 17:07 UTCEG score recomputeFirst assessed: 5.1 MEDIUM
  71. 2026-08-20 17:07 UTCMITRE cvelistV5CVSS v3 → 5.1 · CVSS v4 → 5.1
  72. 2026-08-01 17:51 UTCEG score recompute
  73. 2026-07-26 12:09 UTCEG score recompute
  74. 2026-07-23 03:19 UTCEG score recompute
  75. 2026-07-10 20:12 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54136?
CVE-2026-54136 is a medium-severity vulnerability; its CVE record was published on July 10, 2026. Windmill is an open-source developer platform for internal code: APIs, background jobs, workflows and UIs. Prior to 1.715.0, a resource-scoped API token could read script contents outside its allowed path scope through GET /api/w/{workspace}/scripts/list_search. The route-level scope middleware…
When was the CVE record for CVE-2026-54136 published?
The CVE record for CVE-2026-54136 was published on July 10, 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 October 18, 2026; the record at its source may have been updated since.
Is CVE-2026-54136 actively exploited?
CVE-2026-54136 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54136?
CVE-2026-54136 has a CVSS base score of 5.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54136?
A fix for CVE-2026-54136 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54136 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-54136

Explore →

Is Your Infrastructure Affected by CVE-2026-54136?

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

Book a Demo →Browse All CVEs