Astro has an Authentication Bypass via Double URL Encoding, a bypass for CVE-2025-64765
Published 8 Dec 2025 · Updated 4 Feb 2026
Affected package
- Affected
- <5.15.8
- Fixed in
- 5.15.8
npm install astro@5.15.8Details
Authentication Bypass via Double URL Encoding in Astro
Bypass for CVE-2025-64765 / GHSA-ggxq-hp9w-j794
---
Summary
A double URL encoding bypass allows any unauthenticated attacker to bypass path-based authentication checks in Astro middleware, granting unauthorized access to protected routes. While the original CVE-2025-64765 (single URL encoding) was fixed in v5.15.8, the fix is insufficient as it only decodes once. By using double-encoded URLs like /%2561dmin instead of /%61dmin, attackers can still bypass authentication and access protected resources such as /admin, /api/internal, or any route protected by middleware pathname checks.
Fix
A more secure fix is just decoding once, then if the request has a %xx format, return a 400 error by using something like :
if (containsEncodedCharacters(pathname)) {
// Multi-level encoding detected - reject request
return new Response(
'Bad Request: Multi-level URL encoding is not allowed',
{
status: 400,
headers: { 'Content-Type': 'text/plain' }
}
);
}Is GHSA-whqg-ppgf-wp8c in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected astro, and gives you the command that fixes it.
References
- Linkgithub.com/withastro/astro/security/advisories/GHSA-ggxq-hp9w-j794
- Linkgithub.com/withastro/astro/security/advisories/GHSA-whqg-ppgf-wp8c
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-64765
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-66202
- Linkgithub.com/withastro/astro/commit/6f800813516b07bbe12c666a92937525fddb58ce
- Packagegithub.com/withastro/astro
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.