CVE-2026-59731

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 62% 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
Elevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 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. Version 6.4.7 performs authorization decisions on a partially decoded pathname after reaching the iterative URL decoder limit, while later rewrite route matching performs an additional decodeURI() operation and can resolve the request to a protected route. This issue is fixed in version 6.4.8.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
68(Attend)
EG Risk 68/100SSVC: Attend

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
Severity82% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github_release, github, github_commit.
github Patch Available🟡 PoC Available

Astro 6.4.7 Authorization Bypass via Decode Iteration Limit and Rewrite Path Canonicalization Mismatch · Advisory · withastro/astro · GitHub

https://github.com/withastro/astro/security/advisories/GHSA-vj59-8hwv-xxmv
github_release Patch Available

[email protected]

Patch available: withastro/astro [email protected]

https://github.com/withastro/astro/releases/tag/[email protected]
github_pr

fix(core): encoded URLs

Fix merged in withastro/astro PR #17109 on 2026-06-17 — awaiting tagged release

https://github.com/withastro/astro/pull/17109
github_commit

commit 27c80ea92248 (withastro/astro)

Fix landed in withastro/astro commit 27c80ea92248 — awaiting tagged release

https://github.com/withastro/astro/commit/27c80ea92248993e5fce94b2c26d87d611ab6785

Vendor Advisories for CVE-2026-59731(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
astro—6.4.8—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-59731?
CVE-2026-59731 is a high vulnerability published on July 8, 2026. Astro is a web framework for content-driven websites. Version 6.4.7 performs authorization decisions on a partially decoded pathname after reaching the iterative URL decoder limit, while later rewrite route matching performs an additional decodeURI() operation and can resolve the request to a…
When was CVE-2026-59731 disclosed?
CVE-2026-59731 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59731 actively exploited?
CVE-2026-59731 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 61.7% of all scored CVEs.
What is the CVSS score of CVE-2026-59731?
CVE-2026-59731 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-59731?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59731, 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-59731

Explore →

Is Your Infrastructure Affected by CVE-2026-59731?

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

Start Free Scan →Browse All CVEs