What’s Vulnerable › Vulnerabilities
CVE-2026-59730: @astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect
- Severity: low (CVSS 2.1 v4.0)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.5% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-07-27 · updated 2026-10-24
- Weakness: CWE-601
Description
Astro is a web framework for content-driven websites. In versions 8.1.0 through 11.0.1, when trailingSlash: 'always' is configured, the @astrojs/node standalone server's static file handler appends a trailing slash to request paths and issues a 301 redirect. Paths beginning with /\ (slash-backslash) were not recognized as internal paths, so the handler would echo the raw path back in the Location header. Because browsers treat \ as / per the WHATWG URL specification, the resulting redirect could resolve to an external host. Preconditions for exploitation: trailingSlash: 'always' must be set (non-default; the default is 'ignore'), the request path must not have a file extension in its final segment, and an attacker must deliver the crafted link to a user. This issue has been fixed in version 11.0.2.
Affected products
- withastro astro: from 8.1.0, < 11.0.2
References
- https://github.com/withastro/astro/commit/eb6f97e391ee587747e37609c255c7cd4b9cce3c
- https://github.com/withastro/astro/pull/17252
- https://github.com/withastro/astro/releases/tag/@astrojs/node@11.0.2
- https://github.com/withastro/astro/security/advisories/GHSA-r557-wffq-wvrc
Get alerted when CVE-2026-59730 or the next vulnerability affects your stack