CVE-2026-126361: Astro: XSS via attribute injection in dynamic tag names
Summary When a dynamic tag (const Tag = ...; ) resolves to a string, Astro renders it as a raw HTML element name. The name was filtered to remove characters that could inject attributes, but the filter did not handle /. Because HTML parsers treat / inside a tag as an attribute separator, a tag name such as img/src/onerror=alert(1) was rendered as an element with an onerror attribute.
Published Nov 13, 2026
Affected packages
astro
- Ecosystem
- npm
- Affected
- <= 7.4.4
- Fixed in
- 7.4.5
- Check
npm ls astro
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
When a dynamic tag (const Tag = ...; <Tag />) resolves to a string, Astro renders it as a raw HTML element name. The name was filtered to remove characters that could inject attributes, but the filter did not handle /. Because HTML parsers treat / inside a tag as an attribute separator, a tag name such as img/src/onerror=alert(1) was rendered as an ` element with an onerror` attribute. The JSX renderer used for MDX did not filter string tag names at all.
For example:
---
const Tag = Astro.url.searchParams.get('as') ?? 'div';
---
<Tag>hello</Tag>rendered ?as=img/src/onerror=alert(1) as live HTML.
Impact
Reflected or stored cross-site scripting, but only in applications that use untrusted input (such as a request parameter or an uncontrolled CMS field) as all or part of an element name. Astro itself never derives element names from request data.
Applications that let content choose an element should map that input to a fixed set of known tags. Letting untrusted input choose an element name is unsafe even with a correct filter, because it can still select elements such as script or iframe.
Affected versions
astro <= 7.4.4.
Patches
Fixed in astro 7.4.5. String tag names in .astro dynamic tags, JSX, and MDX now render only the leading valid element name, so characters such as / or = can no longer change the generated markup. Strings that do not start with a valid element name now throw an error.
Workarounds
Upgrade to astro 7.4.5 or later. Before upgrading, do not use untrusted input as an element name, or map it to a fixed set of known tags.
Credits
Reported by @uttej-badwane.
Credited to uttej-badwane.
References
- https://github.com/withastro/astro/security/advisories/GHSA-mh32-jxcr-mh9f
- https://nvd.nist.gov/vuln/detail/CVE-2026-126361
- https://github.com/withastro/astro/pull/18520
- https://github.com/withastro/astro/commit/e023abac912d7cb6af2b9fb5107ef5dabc667096
- https://github.com/withastro/astro/releases/tag/[email protected]
- https://github.com/advisories/GHSA-mh32-jxcr-mh9f
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-126364
Astro: Image endpoint in @astrojs/node can read files from a case-variant sibling of the output directory on case-sensitive filesystems
medium6.3No fixNov 13, 2026CVE-2026-114127
Astro: Arbitrary CSS injection in Astro View Transitions
low2.3Oct 22, 2026CVE-2026-114128
Astro: Reflected/Stored XSS via unescaped <script>/<style> tag content in JSX/MDX rendering
medium6.5Oct 22, 2026CVE-2026-84376
Astro: Authorization bypass from missing path-segment boundary check when stripping the configured base
medium6.3Sep 8, 2026GHSA-26w7-cxv4-gfx2
Astro: Remote code execution through AVIF image optimization
critical9.8Sep 8, 2026CVE-2026-59727
Astro: Cross-site scripting via unescaped transition:* directive values on hydrated islands
low2.1Jul 20, 2026
