CVE-2026-59730

LOWPre-NVD 2.12.1—
EchelonGraph scoreMEDIUM confidence

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

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

Astro is a web framework for content-driven websites. In versions 8.1.0 through 11.0.1, when trailingSlash: 'always' is configured, the @astrojs/node standalone server's static file handler appends a trailing slash to request paths and issues a 301 redirect. Paths beginning with /\ (slash-backslash) were not recognized as internal paths, so the handler would echo the raw path back in the Location header. Because browsers treat \ as / per the WHATWG URL specification, the resulting redirect could resolve to an external host. Preconditions for exploitation: trailingSlash: 'always' must be set (non-default; the default is 'ignore'), the request path must not have a file extension in its final segment, and an attacker must deliver the crafted link to a user. This issue has been fixed in version 11.0.2.

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

Published

July 20, 2026

Last Modified

July 28, 2026

References (4)

Vendor Advisories for CVE-2026-59730(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)
npm(1)
PackageVulnerable rangeFixed inDependents
@astrojs/node—11.0.2—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-59730?
CVE-2026-59730 is a low vulnerability published on July 20, 2026. Astro is a web framework for content-driven websites. In versions 8.1.0 through 11.0.1, when trailingSlash: 'always' is configured, the @astrojs/node standalone server's static file handler appends a trailing slash to request paths and issues a 301 redirect. Paths beginning with /\…
When was CVE-2026-59730 disclosed?
CVE-2026-59730 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59730 actively exploited?
CVE-2026-59730 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 70.8% of all scored CVEs.
What is the CVSS score of CVE-2026-59730?
CVE-2026-59730 has a CVSS v3 base score of 2.1 (NVD).
How do I remediate CVE-2026-59730?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59730, 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-59730

Explore →

Is Your Infrastructure Affected by CVE-2026-59730?

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

Start Free Scan →Browse All CVEs