CVE-2026-25500

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

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

Rack is a modular Ruby web server interface. Prior to versions 2.2.22, 3.1.20, and 3.2.5, Rack::Directory generates an HTML directory index where each file entry is rendered as a clickable link. If a file exists on disk whose basename starts with the javascript: scheme (e.g. javascript:alert(1)), the generated index contains an anchor whose href is exactly javascript:alert(1). Clicking the entry executes JavaScript in the browser (demonstrated with alert(1)). Versions 2.2.22, 3.1.20, and 3.2.5 fix the issue.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity54% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

February 18, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
Patch available. Sources: github_commit, github.
github Patch Available

XSS injection via malicious filename in `Rack::Directory`. · Advisory · rack/rack · GitHub

https://github.com/rack/rack/security/advisories/GHSA-whrj-4476-wvmp
github_commit

commit f2f225f297b9 (rack/rack)

Fix landed in rack/rack commit f2f225f297b9 — awaiting tagged release

https://github.com/rack/rack/commit/f2f225f297b99fbee3d9f51255d41f601fc40aff

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
ruby-rack2.1.4-3, 2.1.4-3+deb11u1, 2.1.4-3+deb11u2, 2.1.4-3+deb11u3, 2.1.4-3+deb11u42.1.4-3+deb11u5
Debian:12(1)
PackageVulnerable rangeFixed inDependents
ruby-rack2.2.13-1~deb12u1 ... 2.2.7-1.1 (6 versions)2.2.22-0+deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
ruby-rack3.1.16-0.1, 3.1.18-1, 3.1.18-1~deb13u13.1.20-0+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
ruby-rack3.1.16-0.1, 3.1.18-1, 3.1.18-1~deb13u1, 3.2.4-13.2.5-1
RubyGems(1)
PackageVulnerable rangeFixed inDependents
rack3.2.0, 3.2.1, 3.2.2, 3.2.3, 3.2.43.2.5

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 25× 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-09-18 20:50 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-30 23:57 UTCOSV refresh
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:48 UTCEPSS rescore
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 35 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 09:46 UTCEG score recompute
  8. 2026-08-14 09:46 UTCVendor advisory
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 02:02 UTCEG score recompute
  11. 2026-08-13 02:02 UTCVendor advisory
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-11 13:42 UTCEPSS rescore
  14. 2026-08-11 07:25 UTCEG score recompute
  15. 2026-08-11 07:25 UTCVendor advisory
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-09 14:05 UTCEG score recompute
  18. 2026-08-09 14:05 UTCVendor advisory
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-07 21:40 UTCEG score recompute
  22. 2026-08-07 21:40 UTCVendor advisory
  23. 2026-08-06 13:46 UTCEPSS rescore
  24. 2026-08-06 03:34 UTCEG score recompute
  25. 2026-08-06 03:34 UTCVendor advisory
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-04 15:10 UTCEPSS rescore
  28. 2026-08-03 10:36 UTCEPSS rescore
  29. 2026-08-02 20:19 UTCEG score recompute
  30. 2026-08-02 20:19 UTCVendor advisory
  31. 2026-08-02 02:26 UTCEPSS rescore
  32. 2026-07-30 16:27 UTCEPSS rescore
  33. 2026-07-30 01:30 UTCEPSS rescore
  34. 2026-07-28 15:36 UTCEPSS rescore
  35. 2026-07-27 13:28 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-25500?
CVE-2026-25500 is a medium vulnerability published on February 18, 2026. Rack is a modular Ruby web server interface. Prior to versions 2.2.22, 3.1.20, and 3.2.5, Rack::Directory generates an HTML directory index where each file entry is rendered as a clickable link. If a file exists on disk whose basename starts with the javascript: scheme (e.g. javascript:alert(1)),…
When was CVE-2026-25500 disclosed?
CVE-2026-25500 was first published in the National Vulnerability Database on February 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25500 actively exploited?
CVE-2026-25500 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 85.5% of all scored CVEs.
What is the CVSS score of CVE-2026-25500?
CVE-2026-25500 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-25500?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25500, 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-25500

Explore →

Is Your Infrastructure Affected by CVE-2026-25500?

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