# CVE-2025-64765: Astro middleware authentication checks based on url.pathname can be bypassed via url encoded values

> Attackers can bypass middleware authentication checks in Astro by using URL-encoded paths, allowing unauthorized access to protected routes.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Nov 2025
- **Updated:** 20 Nov 2025
- **Also known as:** GHSA-ggxq-hp9w-j794

## What is CVE-2025-64765?

CVE-2025-64765 is a medium-severity authentication bypass vulnerability in withastro astro, published on 19 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-64765?

2 open source packages ship an affected version, including astro. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `astro` | npm | All versions | 5.15.8 |
| `astro` | npm | All versions | 5.15.8 |

Products: Astro Astro.

## How do I fix CVE-2025-64765?

Upgrade astro to 5.15.8 or later.

## Is CVE-2025-64765 being exploited?

There is no known exploitation of CVE-2025-64765 in the wild and no public exploit code.

## Other vulnerabilities in withastro astro

- [CVE-2024-56159](https://insights.sbomify.com/CVE-2024-56159/): Server source code is exposed to the public if sourcemaps are enabled (high 7.8)
- [CVE-2026-54299](https://insights.sbomify.com/CVE-2026-54299/): Astro: Host header SSRF in prerendered error page fetch (high 7.5)
- [CVE-2025-59837](https://insights.sbomify.com/CVE-2025-59837/): astro allows bypass of image proxy domain validation leading to SSRF and potential XSS (high 7.2)
- [CVE-2026-50146](https://insights.sbomify.com/CVE-2026-50146/): Astro: Reflected XSS via unescaped slot name (high 7.1)
- [CVE-2025-64764](https://insights.sbomify.com/CVE-2025-64764/): Astro is vulnerable to Reflected XSS via the server islands feature (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64765 and fix it if it is affected.

What it is: CVE-2025-64765 is a medium-severity authentication bypass vulnerability in withastro astro, published on 19 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64765 in the wild and no public exploit code.

Affected packages and fixed versions:
- astro (npm): affected all versions; fixed in 5.15.8
- astro (npm): affected all versions; fixed in 5.15.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64765/ (Markdown: https://insights.sbomify.com/CVE-2025-64765/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64765
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64765
- OSV: https://osv.dev/vulnerability/CVE-2025-64765

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64765/
Summaries are generated and may contain mistakes; the official description above is the record.