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.
References
| Link | Resource |
|---|---|
| https://github.com/withastro/astro/commit/6f800813516b07bbe12c666a92937525fddb58ce | Patch |
| https://github.com/withastro/astro/security/advisories/GHSA-ggxq-hp9w-j794 | Exploit Mitigation Third Party Advisory |
Configurations
History
No history.
Information
Published : 2025-11-19 17:15
Updated : 2025-11-25 15:11
NVD link : CVE-2025-64765
Mitre link : CVE-2025-64765
CVE.ORG link : CVE-2025-64765
JSON object : View
Products Affected
astro
- astro
CWE
CWE-22
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
