CVE-2026-54136

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% 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, secondary
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.1(medium)
EG Risk
23(Track)
EG Risk 23/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
Severity51% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

July 10, 2026

Last Modified

August 21, 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_pr

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 Patch Available

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.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
windmill-api—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 / 20× 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-08-30 06:19 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-28 04:29 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-27 04:01 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-26 03:34 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 23:20 UTCEG score recompute
  11. 2026-08-23 23:05 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 22:42 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 22:27 UTCEG score recompute
  16. 2026-08-21 22:01 UTCEG score recompute
  17. 2026-08-20 17:35 UTCEG score recompute
  18. 2026-08-20 17:07 UTCEG score recompute▲ 5.10
  19. 2026-08-20 17:07 UTCMITRE cvelistV5CVSS v3 → 5.1 · CVSS v4 → 5.1
  20. 2026-08-01 17:51 UTCEG score recompute
  21. 2026-07-26 12:09 UTCEG score recompute
  22. 2026-07-23 03:19 UTCEG score recompute
  23. 2026-07-10 20:12 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54136?
CVE-2026-54136 is a medium vulnerability 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/listsearch. The route-level scope middleware…
When was CVE-2026-54136 disclosed?
CVE-2026-54136 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54136 actively exploited?
CVE-2026-54136 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.6% of all scored CVEs.
What is the CVSS score of CVE-2026-54136?
CVE-2026-54136 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-54136?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54136, 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-54136

Explore →

Is Your Infrastructure Affected by CVE-2026-54136?

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

Start Free Scan →Browse All CVEs