# CVE-2026-92106: lazy_html serializes SVG and MathML style and script text unescaped, allowing mutation XSS

> Attackers can execute arbitrary JavaScript via mutation XSS when untrusted HTML containing SVG or MathML is parsed and serialized by the lazy_html library.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** EEF-CVE-2026-92106, GHSA-8rqp-v692-v82q

## What is CVE-2026-92106?

CVE-2026-92106 is a low-severity cross-site scripting vulnerability in dashbitco lazy_html, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in dashbitco lazy_html allows mutation XSS via a parse and serialize round-trip of attacker-supplied HTML.

LazyHTML.to_html/2 and LazyHTML.Tree.to_html/2 decide whether to escape an element's text from its tag name alone. A style or script element inside SVG or MathML foreign content is parsed with character references decoded, but is serialized as an HTML raw-text element, so its text is emitted unescaped. Encoded markup such as &lt;/style&gt;&lt;img src=x onerror=...&gt; inside <svg><style> therefore closes the element on re-parse and becomes live markup. Applications that parse untrusted HTML with lazy_html, filter the document or tree, and serialize it for display are affected, since the payload is a plain text node that no element or attribute filter sees.

This issue affects lazy_html: from 0.1.0 before 0.1.13.

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

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

1 open source package ship an affected version, including lazy_html.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lazy_html` | Hex | From 0.1.0 | 0.1.13 |

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

Upgrade lazy_html to 0.1.13 or later.

## Is CVE-2026-92106 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92106 is a low-severity cross-site scripting vulnerability in dashbitco lazy_html, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92106 in the wild and no public exploit code.

Affected packages and fixed versions:
- lazy_html (Hex): affected from 0.1.0; fixed in 0.1.13

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-92106/ (Markdown: https://insights.sbomify.com/CVE-2026-92106/index.md)
```

## Sources

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

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