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.3%, top 82% 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
Trending — 3 sources updated this weekElevated
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 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)
EPSS
18.4%
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_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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 12× 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-07-11 19:46 UTCEG score recompute
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 07:18 UTCEG score recompute
  5. 2026-07-10 18:50 UTCEG score recompute
  6. 2026-07-10 06:22 UTCEG score recompute
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 17:53 UTCEG score recompute
  10. 2026-07-09 05:25 UTCEG score recompute
  11. 2026-07-08 16:56 UTCEG score recompute
  12. 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 18.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.