CVE-2025-55207: @astrojs/node's trailing slash handling causes open redirect issue
Summary Following https://github.com/withastro/astro/security/advisories/GHSA-cq8c-xv66-36gw, there's still an Open Redirect vulnerability in a subset of Astro deployment scenarios. Details Astro 5.12.8 fixed a case where https://example.com//astro.build/press would redirect to the external origin //astro.build/press.
Published Aug 15, 2025
Affected packages
@astrojs/node
- Ecosystem
- npm
- Affected
- <= 9.4.0
- Fixed in
- 9.4.1
- Check
npm ls @astrojs/node
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Following https://github.com/withastro/astro/security/advisories/GHSA-cq8c-xv66-36gw, there's still an Open Redirect vulnerability in a subset of Astro deployment scenarios.
Details
Astro 5.12.8 fixed a case where https://example.com//astro.build/press would redirect to the external origin //astro.build/press. However, with the Node deployment adapter in standalone mode and trailingSlash set to "always" in the Astro configuration, https://example.com//astro.build/press still redirects to //astro.build/press.
Proof of Concept
- Create a new minimal Astro project (
[email protected]) - Configure it to use the Node adapter (
@astrojs/[email protected]) and force trailing slashes: ```js // astro.config.mjs import { defineConfig } from 'astro/config'; import node from '@astrojs/node';
export default defineConfig({ trailingSlash: 'always', adapter: node({ mode: 'standalone' }), });
3. Build the site by running `astro build`.
4. Run the server, e.g. with `astro preview`.
5. Append `//astro.build/press` to the preview URL, e.g. <http://localhost:4321//astro.build/press>
6. The site will redirect to the external Astro Build origin.
#### Example reproduction
1. Open [this StackBlitz reproduction](https://stackblitz.com/edit/github-4fvpfhcz-nyfj2mbf).
2. Open the preview in a separate window so the StackBlitz embed doesn't cause security errors.
3. Append `//astro.build/press` to the preview URL, e.g. `https://x.local-corp.webcontainer.io//astro.build/press`.
4. See it redirect to the external Astro Build origin.
### Impact
This is classified as an Open Redirection vulnerability (CWE-601). It affects any user who clicks on a specially crafted link pointing to the affected domain. Since the domain appears legitimate, victims may be tricked into trusting the redirected page, leading to possible credential theft, malware distribution, or other phishing-related attacks.
No authentication is required to exploit this vulnerability. Any unauthenticated user can trigger the redirect by clicking a malicious link.Credited to florian-lefebvre, ematipico, Fryuni, delucis.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-126364
Astro: Image endpoint in @astrojs/node can read files from a case-variant sibling of the output directory on case-sensitive filesystems
medium6.3No fixNov 13, 2026CVE-2026-102984
Astro: Malformed port in the Host header can crash the Node adapter
high8.2Sep 30, 2026CVE-2026-59730
@astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect
low2.1Jul 20, 2026CVE-2026-41322
Astro: Cache Poisoning due to incorrect error handling when if-match header is malformed
medium5.3Apr 23, 2026CVE-2026-29772
Astro: Memory exhaustion DoS due to missing request body size limit in Server Islands
medium5.9Mar 24, 2026CVE-2026-27729
Astro has memory exhaustion DoS due to missing request body size limit in Server Actions
medium5.9Feb 25, 2026
