GHSA-mh32-jxcr-mh9f

Suggest an improvement
Source
https://github.com/advisories/GHSA-mh32-jxcr-mh9f
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-mh32-jxcr-mh9f/GHSA-mh32-jxcr-mh9f.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-mh32-jxcr-mh9f
Aliases
Published
2026-11-13T18:39:54Z
Modified
2026-11-13T19:15:05Z
Severity
  • 2.3 (Low) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N CVSS Calculator
Summary
Astro: XSS via attribute injection in dynamic tag names
Details

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 <img> 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.

Database specific
{
    "cwe_ids": [
        "CWE-184",
        "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-11-13T18:39:54Z",
    "nvd_published_at": "2026-11-13T00:20:11Z",
    "severity": "LOW"
}
References

Affected packages

npm / astro

Package

Affected ranges

Type
SEMVER
Events
Introduced
0 Unknown introduced version / All previous versions are affected
Fixed
7.4.5

Database specific

last_known_affected_version_range
"<= 7.4.4"
source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-mh32-jxcr-mh9f/GHSA-mh32-jxcr-mh9f.json"