Back to CVE records
Medium 6.9Published Nov 19, 2025

CVE-2025-64765Astro middleware authentication checks based on url.pathname can be bypassed via url encoded values

Updated under an hour ago ()

Does this affect you?

It affects withastro astro and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Astro is a web framework. Prior to version 5.15.8, a mismatch exists between how Astro normalizes request paths for routing/rendering and how the application’s middleware reads the path for validation checks. Astro internally applies decodeURI() to determine which route to render, while the middleware uses context.url.pathname without applying the same normalization (decodeURI). This discrepancy may allow attackers to reach protected routes using encoded path variants that pass routing but bypass validation checks. This issue has been patched in version 5.15.8.

CVSS
6.9 MEDIUM (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Weakness (CWE)
CWE-22
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Analyzed
Record last updated
Nov 20, 2025
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
withastro astro
withastro:astro (from the name)
before 5.15.8
CNA record
astro astro
astro:astro
before 5.15.8
NVD

References

  • x-refsource-confirm, exploit, mitigation, third-party-advisory
  • x-refsource-misc, patch

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.