CVE-2026-59727: Astro Cross-Site Scripting Vulnerability
LOWCVE-2026-59727 is a LOW cross-site scripting vulnerability (CWE-116: Improper Encoding or Escaping of Output) affecting Astro libraries in the npm ecosystem. The issue involves cross-site scripting via unescaped transition:* directive values on hydrated islands. Remediation is available by upgrading affected packages to version 7.0.4.
CVE-2026-59727 at a Glance
How to Fix CVE-2026-59727
To remediate this vulnerability, upgrade all affected Astro dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install astro@7.0.4
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls astro
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-59727, inspect your project dependencies using npm:
npm ls astro
Analyze the terminal output to locate any version of Astro in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 7.0.4), your application is affected.
Note: The npm ls astro command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-116: Improper Encoding or Escaping of Output, where the product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. as a result, the intended structure of the message is not preserved. In Astro, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-59727 Affected Astro Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
astro
|
npm |
≥ 3.10.0
< 7.0.4
|
7.0.4
|
References
Frequently Asked Questions
What is CVE-2026-59727?
Which Astro versions are affected?
What version fixes CVE-2026-59727?
Is astro affected?
What CWE is associated with CVE-2026-59727?
How can I check npm dependencies for CVE-2026-59727?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-7pw4-f3q4-r2p2",
"modified" : "2026-08-12T20:37:24Z",
"published" : "2026-07-20T23:21:02Z",
"aliases" : [ "CVE-2026-59727" ],
"summary" : "Astro: Cross-site scripting via unescaped transition:* directive values on hydrated islands",
"details" : "### Summary\n\nWhen 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).\n\n### Severity\n\nAlthough a generic reflected XSS scores in the Medium range, exploitation here 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 mitigating precondition places the real-world severity at Low.\n\n### Details\n\nIn `generateHydrateScript()` (`packages/astro/src/runtime/server/hydration.ts`), every island property is HTML-escaped before serialization — the `attrs`, `props`, and `opts` assignments all pass through `escapeHTML()`. The transition directives, however, were copied verbatim:\n\n```ts\ntransitionDirectivesToCopyOnIsland.forEach((name) => {\n if (typeof props[name] !== 'undefined') {\n island.props[name] = props[name]; // not escaped\n }\n});\n```\n\nThe `<astro-island>` element is serialized via `renderElement('astro-island', island, false)` with `shouldEscape=false`, and `toAttributeString()` returns the value unchanged in that mode. As a result there is no downstream re-escaping, and the raw directive value reaches the HTML response. This is the same output sink previously addressed for slot names in GHSA-8hv8-536x-4wqp.\n\nThe affected directives are:\n\n- `data-astro-transition-scope` (`transition:scope`)\n- `data-astro-transition-persist` (`transition:persist`)\n- `data-astro-transition-persist-props` (`transition:persist-props`)\n\nNote that `transition:persist` is typed `boolean | string`, so passing a string value is a supported use of the API.\n\n### Proof of Concept\n\nA component that reflects a query parameter into a transition directive:\n\n```astro\n---\nconst persist = Astro.url.searchParams.get('persist') ?? 'default';\n---\n<Island client:load transition:persist={persist} />\n```\n\nRequest:\n\n```\nhttps://example.com/?persist=\"><img src=x onerror=alert(document.domain)>\n```\n\nRendered output (before the fix):\n\n```html\n<astro-island … data-astro-transition-persist=\"\"><img src=x onerror=alert(document.domain)>></astro-island>\n```\n\nThe `\"` closes the attribute and the injected `<img onerror=…>` executes in the victim's browser.\n\n### Impact\n\nReflected XSS. An attacker who can induce a victim to visit a crafted URL can execute arbitrary script in the victim's session on the origin, subject to the requirement that the target application reflects untrusted input into one of the affected transition directives.\n\n### Affected Versions\n\n`astro >= 3.10.0, < 7.0.4` (introduced in 3.10.0, PR #7861).\n\n### Patched Versions\n\n`astro >= 7.0.4`. Fixed in PR #17212 by HTML-escaping transition directive values before they are rendered onto the island element.\n\n### Workarounds\n\nDo not pass untrusted or request-derived input into `transition:persist`, `transition:scope`, or `transition:persist-props`. If such input is required, HTML-escape or strictly validate it before passing it to the directive. Upgrading to `astro@7.0.4` or later removes the need for manual mitigation.\n\n### Credits\n\nReported by @jlgore.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "astro"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.10.0"
}, {
"fixed" : "7.0.4"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/withastro/astro/security/advisories/GHSA-7pw4-f3q4-r2p2"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-59727"
}, {
"type" : "WEB",
"url" : "https://github.com/withastro/astro/pull/17212"
}, {
"type" : "WEB",
"url" : "https://github.com/withastro/astro/commit/7ba0bb1dc7516e88caff9abd7767322af44b0294"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/withastro/astro"
}, {
"type" : "WEB",
"url" : "https://github.com/withastro/astro/releases/tag/astro@7.0.4"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-116", "CWE-79", "CWE-83" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-20T23:21:02Z",
"nvd_published_at" : "2026-07-27T20:16:40Z"
}
}