# CVE-2025-54793: Astro: Duplicate trailing slash feature can lead to Open Redirects

> Attackers can redirect users to malicious external domains via crafted URLs in Astro SSR sites, facilitating phishing attacks.

- **Severity:** Medium 5.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Aug 2025
- **Updated:** 8 Aug 2025
- **Also known as:** GHSA-cq8c-xv66-36gw

## What is CVE-2025-54793?

CVE-2025-54793 is a medium-severity vulnerability in withastro astro, published on 8 Aug 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 for content-driven websites. In versions 5.2.0 through 5.12.7, there is an Open Redirect vulnerability in the trailing slash redirection logic when handling paths with double slashes. This allows an attacker to redirect users to arbitrary external domains by crafting URLs such as https://mydomain.com//malicious-site.com/. This increases the risk of phishing and other social engineering attacks. This affects sites that use on-demand rendering (SSR) with the Node or Cloudflare adapters. It does not affect static sites, or sites deployed to Netlify or Vercel. This issue is fixed in version 5.12.8. To work around this issue at the network level, block outgoing redirect responses with a Location header value that starts with `//`.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

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.12.8 |
| `astro` | npm | From 5.2.0 | 5.12.8 |

Products: Astro Astro.

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

Upgrade astro to 5.12.8 or later.

## Is CVE-2025-54793 being exploited?

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

Public exploit code:

- Group project — CVE-2025-54793 detection & mitigation (Bhuvanesh, Shiva, Emma) (github_poc): https://github.com/bhuvi-labs/ict279-cve-2025-54793
- Astro SSR - Open Redirect (nuclei): http/cves/2025/CVE-2025-54793.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-54793 and fix it if it is affected.

What it is: CVE-2025-54793 is a medium-severity vulnerability in withastro astro, published on 8 Aug 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-54793 exists.

Affected packages and fixed versions:
- astro (npm): affected from 5.2.0; fixed in 5.12.8
- astro (npm): affected from 5.2.0; fixed in 5.12.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-54793/ (Markdown: https://insights.sbomify.com/CVE-2025-54793/index.md)
```

## Sources

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

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