# CVE-2025-64745: Astro development server error page vulnerable to reflected Cross-site Scripting

> Attackers can execute arbitrary JavaScript in developer browsers via malicious URLs in Astro's development server error pages when trailingSlash is enabled.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Nov 2025
- **Updated:** 13 Nov 2025
- **Also known as:** GHSA-w2vj-39qv-7vh7

## What is CVE-2025-64745?

CVE-2025-64745 is a low-severity cross-site scripting vulnerability in withastro astro, published on 13 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Astro is a web framework. Starting in version 5.2.0 and prior to version 5.15.6, a Reflected Cross-Site Scripting (XSS) vulnerability exists in Astro's development server error pages when the `trailingSlash` configuration option is used. An attacker can inject arbitrary JavaScript code that executes in the victim's browser context by crafting a malicious URL. While this vulnerability only affects the development server and not production builds, it could be exploited to compromise developer environments through social engineering or malicious links. Version 5.15.6 fixes the issue.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `astro` | npm | From 5.2.0 | 5.15.6 |
| `astro` | npm | From 5.2.0 | 5.15.6 |

Products: Astro Astro.

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

Upgrade astro to 5.15.6 or later.

## Is CVE-2025-64745 being exploited?

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

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

What it is: CVE-2025-64745 is a low-severity cross-site scripting vulnerability in withastro astro, published on 13 Nov 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64745 exists.

Affected packages and fixed versions:
- astro (npm): affected from 5.2.0; fixed in 5.15.6
- astro (npm): affected from 5.2.0; fixed in 5.15.6

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

## Sources

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

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