CVE-2025-64765
BaseFortify
Publication date: 2025-11-19
Last updated on: 2025-11-25
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| astro | astro | to 5.15.8 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Astro web framework prior to version 5.15.8. It arises because Astro normalizes request paths for routing/rendering using decodeURI(), but the application's middleware reads the path without applying the same normalization. This mismatch allows attackers to use encoded path variants to access protected routes that should be restricted, bypassing validation checks.
How can this vulnerability impact me? :
An attacker could exploit this vulnerability to access protected routes in an Astro-based application by using encoded path variants that bypass middleware validation. This could lead to unauthorized access to sensitive parts of the application or data exposure.
What immediate steps should I take to mitigate this vulnerability?
The immediate step to mitigate this vulnerability is to upgrade Astro to version 5.15.8 or later, where the issue has been patched.