# CVE-2026-114128: Astro: Reflected/Stored XSS via unescaped <script>/<style> tag content in JSX/MDX rendering


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-98hj-9722-w3j8

## What is CVE-2026-114128?

CVE-2026-114128 is a medium-severity vulnerability in withastro astro, published on 21 Oct 2026. 

### Official description

Astro is a web framework for content-driven websites. Prior to 7.3.2, Astro's JSX and MDX rendering pipeline treats string children of script and style elements as trusted HTML without distinguishing compiler-generated literal content from dynamic expression values. An application that passes attacker-controlled data directly as a dynamic child can allow a value containing a closing script or style tag to terminate the element and inject arbitrary HTML and JavaScript. Other JSX expression contexts escape dynamic strings automatically; the issue is limited to script and style children rendered through the astro:jsx renderer, including MDX components. Successful exploitation can produce reflected or stored cross-site scripting under the application's origin. This issue is fixed in 7.3.2.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-114128?

2 open source packages ship an affected version, including astro.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `astro` | npm | All versions | 7.3.2 |
| `astro` | npm | All versions | 7.3.2 |

## How do I fix CVE-2026-114128?

Upgrade astro to 7.3.2 or later.

## Is CVE-2026-114128 being exploited?

There is no known exploitation of CVE-2026-114128 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114128 and fix it if it is affected.

What it is: CVE-2026-114128 is a medium-severity vulnerability in withastro astro, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114128 in the wild and no public exploit code.

Affected packages and fixed versions:
- astro (npm): affected all versions; fixed in 7.3.2
- astro (npm): affected all versions; fixed in 7.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114128/ (Markdown: https://insights.sbomify.com/CVE-2026-114128/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114128
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114128
- OSV: https://osv.dev/vulnerability/CVE-2026-114128

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114128/
Summaries are generated and may contain mistakes; the official description above is the record.