Quick answers
- Is CVE-2026-59729 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59729 being exploited in the wild.
- How severe is CVE-2026-59729?
- Medium severity, with a CVSS score of 4, published 27 July 2026.
- Which products and versions are affected?
- astro (npm) < 7.0.6, SEMVER:introduced=0,fixed=7.0.6.
- Is there a fix for CVE-2026-59729?
- Yes. astro (npm): upgrade to 7.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59729 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59729?
- Check whether you run astro (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- astro (npm): upgrade to 7.0.6 or later
npm install astro@7.0.6
Technical details
A cross-site scripting (XSS) vulnerability exists in Astro's server-side rendering (SSR) runtime. While a previous fix (CVE-2026-54298) hardened the 'addAttribute' function, a separate rendering path in 'renderHTMLElement' (packages/astro/src/runtime/server/render/dom.ts) was overlooked. This path interpolates attribute names raw while only escaping the values. An attacker can provide malicious property keys containing characters like quotes, brackets, or whitespace to inject event handlers or script tags. This is reachable when the SSR environment (such as Deno, Bun, or Node with a DOM shim) defines a global HTMLElement and a native HTMLElement subclass is used as a component. The issue is fixed in version 7.0.6.
Affected products
- withastro Astro < 7.0.6
Identifiers
- CVE-2026-59729
- GHSA-f48w-9m4c-m7f5
Timeline
- 2026-07-01: disclosed: Pull request submitted to fix the issue
- 2026-07-02: patched: Version 7.0.6 released
- 2026-07-27: advisory: CVE-2026-59729 published