CVE-2026-59727: withastro astro · Cross-site Scripting
Affects withastro astroSource CVE Database V5
Not known to be exploited · CVSS 2.1 Low : upgrade to 7.0.4 when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 7.0.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/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 7.0.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| withastroastro | Affected
| Fixed in
|
AI-suggested
This vulnerability is fixed in Astro version 7.0.4. Users should upgrade to version 7.0.4 or later to remediate the issue. Applications that do not pass untrusted input into the affected transition directives are not vulnerable. No additional mitigation steps are indicated.
Description
Astro is a web framework for content-driven websites. In versions 3.10.0 through 7.0.3, when a transition:persist, transition:scope, or transition:persist-props directive is applied to a client-hydrated (client:*) component, Astro copied the directive value onto the rendered <astro-island> element without HTML-escaping it. If a developer reflects attacker-controlled input into one of these directives, an attacker can break out of the attribute and inject arbitrary HTML/JavaScript into the server-rendered output, resulting in reflected cross-site scripting (XSS). Exploitation requires the application developer to have written a non-idiomatic pattern — passing untrusted, request-derived input directly into a transition directive. Astro applications that do not route untrusted input into these directives are unaffected. This issue has been fixed in version 7.0.4.
References
- github.com/withastro/astro/security/advisories/GHSA-7pw4-f3q4-r2p2 (opens in a new tab)
- github.com/withastro/astro/pull/17212 (opens in a new tab)
- github.com/withastro/astro/commit/7ba0bb1dc7516e88caff9abd7767322af44b0294 (opens in a new tab)
- github.com/withastro/astro/releases/tag/astro@7.0.4 (opens in a new tab)