# CVE-2025-64525: Astro vulnerable to URL manipulation via headers, leading to middleware and CVE-2025-61925 bypass

> Attackers can bypass middleware protections and cause SSRF or cache poisoning by manipulating unsanitized forwarded headers in on-demand rendering.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-hr2q-hp5q-x767

## What is CVE-2025-64525?

CVE-2025-64525 is a medium-severity server-side request forgery vulnerability in withastro astro, published on 13 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. In Astro versions 2.16.0 up to but excluding 5.15.5 which utilizeon-demand rendering, request headers `x-forwarded-proto` and `x-forwarded-port` are insecurely used, without sanitization, to build the URL. This has several consequences, the most important of which are: middleware-based protected route bypass (only via `x-forwarded-proto`), DoS via cache poisoning (if a CDN is present), SSRF (only via `x-forwarded-proto`), URL pollution (potential SXSS, if a CDN is present), and WAF bypass. Version 5.15.5 contains a patch.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `astro` | npm | From 2.16.0 | 5.15.5 |
| `astro` | npm | From 2.16.0 | 5.15.5 |

Products: Astro Astro.

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

Upgrade astro to 5.15.5 or later.

## Is CVE-2025-64525 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64525 exists.

Public exploit code:

- Astro - Broken Access Control (nuclei): http/cves/2025/CVE-2025-64525.yaml

## 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-64525 and fix it if it is affected.

What it is: CVE-2025-64525 is a medium-severity server-side request forgery vulnerability in withastro astro, published on 13 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64525 exists.

Affected packages and fixed versions:
- astro (npm): affected from 2.16.0; fixed in 5.15.5
- astro (npm): affected from 2.16.0; fixed in 5.15.5

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-64525/ (Markdown: https://insights.sbomify.com/CVE-2025-64525/index.md)
```

## Sources

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

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