@astrojs/node's trailing slash handling causes open redirect issueGHSA-9x9c-ghc5-jhw9
Fix: withastro/astro@5fc3c59GHSA-9x9c-ghc5-jhw9 is a Open Redirect vulnerability in @astrojs/node. A fix is available for @astrojs/node — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-9x9c-ghc5-jhw9.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@astrojs/nodenpmDescription
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:// astro.config.mjs import { defineConfig } from 'astro/config'; import node from '@astrojs/node'; export default defineConfig({ trailingSlash: 'always', adapter: node({ mode: 'standalone' }), }); - Build the site by running
astro build. - Run the server, e.g. with
astro preview. - Append
//astro.build/pressto the preview URL, e.g. http://localhost:4321//astro.build/press - The site will redirect to the external Astro Build origin.
Example reproduction
- Open this StackBlitz reproduction.
- Open the preview in a separate window so the StackBlitz embed doesn't cause security errors.
- Append
//astro.build/pressto the preview URL, e.g.https://x.local-corp.webcontainer.io//astro.build/press. - 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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @astrojs/node | all versions | 9.4.1npm install @astrojs/node@9.4.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @astrojs/node, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @astrojs/node to 9.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9x9c-ghc5-jhw9 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.
Frequently Asked Questions
Is GHSA-9x9c-ghc5-jhw9 in your dependencies?
Find it across npm, including transitive dependencies.