Authentication bypass via double-encoded path mismatch
Published Dec 8, 2025 · Updated Dec 9, 2025
Authentication bypass in Astro before 5.15.8 allows remote attackers to access routes protected by pathname-based middleware checks. Astro normalizes a request path for routing but exposes a pathname decoded only once to middleware, so a double-encoded path resolves to a protected route after passing a nonmatching authorization comparison. The application must use Astro middleware to authorize specific pathnames; exploitation is unauthenticated and can expose or alter resources reachable through those routes.
Summary
What happened
Authentication bypass in Astro before 5.15.8 allows remote attackers to access routes protected by pathname-based middleware checks. Astro normalizes a request path for routing but exposes a pathname decoded only once to middleware, so a double-encoded path resolves to a protected route after passing a nonmatching authorization comparison. The application must use Astro middleware to authorize specific pathnames; exploitation is unauthenticated and can expose or alter resources reachable through those routes.
The record
- CVE
- CVE-2025-66202
- Published
- Dec 8, 2025
- Updated
- Dec 9, 2025
- Vendor
- Astro Technology Company
- Product
- Astro
- Classifications
- CWE-647, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 8, 2025CVE publishedPublication date reported by the CVE source.
- Dec 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.15.8
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo