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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/withastro/astro/commit/6f800813516b07bbe12c666a92937525fddb58ce Patch
- https://github.com/withastro/astro/security/advisories/GHSA-ggxq-hp9w-j794 Exploit, Mitigation, Third Party Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.9 · astroNVD modified 2026-10-18 20:10
Affected (CPE criteria) 1
cpe:2.3:a:astro:astro:*:*:*:*:*:node.js:*:*
References 2
- https://github.com/withastro/astro/commit/6f800813516b07bbe12c666a92937525fddb58ce Patch
- https://github.com/withastro/astro/security/advisories/GHSA-ggxq-hp9w-j794 Exploit, Mitigation, Third Party Advisory