CVE-2026-59730: withastro astro · Open Redirect
Affects withastro astroSource CVE Database V5
Not known to be exploited · CVSS 2.1 Low : upgrade to 11.0.2 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 11.0.2
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade withastro astro to 11.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| withastroastro | Affected
| Fixed in
|
AI-suggested
Upgrade Astro to version 11.0.2 or later, where this open redirect vulnerability is fixed. If upgrading is not immediately possible, avoid using the trailingSlash: 'always' configuration in the @astrojs/node standalone server to prevent exposure. Monitor vendor advisories for any additional guidance.
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.
References
- github.com/withastro/astro/security/advisories/GHSA-r557-wffq-wvrc (opens in a new tab)
- github.com/withastro/astro/pull/17252 (opens in a new tab)
- github.com/withastro/astro/commit/eb6f97e391ee587747e37609c255c7cd4b9cce3c (opens in a new tab)
- github.com/withastro/astro/releases/tag/@astrojs/node@11.0.2 (opens in a new tab)