CVE-2026-59730
CVE-2026-59730 · @astrojs/node: Backslash-prefixed paths not recognized as internal by trailing-slash redirect
This page contains facts from public vulnerability sources. Check the original advisory before updating.
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.
CVSS 2.1 · Low · EPSS 0.5% · Fix available
- Published
- Updated
Stack: node
Affected products and versions
astro
- Versions
- >= 8.1.0, < 11.0.2: Affected
No fix published
@astrojs/node npm
- Affected ranges
- SEMVER: ≥ 8.1.0, < 11.0.2
Update to 11.0.2
Original sources
- https://github.com/withastro/astro/security/advisories/GHSA-r557-wffq-wvrc
- https://github.com/withastro/astro/pull/17252
- https://github.com/withastro/astro/commit/eb6f97e391ee587747e37609c255c7cd4b9cce3c
- https://github.com/withastro/astro/releases/tag/@astrojs/[email protected]
- https://nvd.nist.gov/vuln/detail/CVE-2026-59730