# CVE-2026-83605: xmldom: Attribute name injection via setAttribute() bypasses requireWellFormed

> Attackers can inject malicious attributes into XML output via setAttribute, leading to XSS in browser-consumed content.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** AZL-99347, CLSA-2026-1790458285, DEBIAN-CVE-2026-83605, ECHO-f69a-fdb4-9b18, GHSA-4w3w-2rp5-g8jm, MINI-542c-29pm-69hv, MINI-7g94-jhvj-xwvx, MINI-c8v8-88xr-ghvv, MINI-f7j3-wfhf-9c4q, ROOT-APP-NPM-CVE-2026-83605, ROOT-APP-NPM-GHSA-4w3w-2rp5-g8jm, UBUNTU-CVE-2026-83605

## What is CVE-2026-83605?

CVE-2026-83605 is a high-severity cross-site scripting vulnerability in @xmldom xmldom, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.14 and 0.9.11, and in xmldom version 0.6.0 and earlier, Element.setAttribute() calls the private _createAttribute(name) path without validating the attribute name, while Document.createAttribute(name) validates against QName. XMLSerializer.serializeToString() emits attribute names verbatim, and requireWellFormed: true did not validate them, so a crafted name can terminate the intended attribute and inject additional attributes, including event handlers, into browser-consumed output; synthesized xmlns:PREFIX declarations expose the same unchecked-name boundary. This issue is fixed in @xmldom/xmldom versions 0.8.14 and 0.9.11; no fixed version is available for xmldom.

Weakness: CWE-91 (XML Injection)

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

6 open source packages ship an affected version, including @xmldom/xmldom and xmldom.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@xmldom/xmldom` | npm | From 0.7.0 | 0.8.14 |
| `@xmldom/xmldom` | npm | From 0.7.0 | 0.8.14 |
| `@xmldom/xmldom` | npm | From 0.9.0 | 0.9.11 |
| `@xmldom/xmldom` | npm | From 0.9.0 | 0.9.11 |
| `xmldom` | npm | All versions to 0.6.0 | None |
| `xmldom` | npm | All versions to 0.6.0 | None |

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

Upgrade @xmldom/xmldom to a fixed version for your release line: 0.8.14 or 0.9.11.

## Is CVE-2026-83605 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-83605 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-83605 is a high-severity cross-site scripting vulnerability in @xmldom xmldom, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-83605 exists.

Affected packages and fixed versions:
- @xmldom/xmldom (npm): affected from 0.7.0; fixed in 0.8.14
- @xmldom/xmldom (npm): affected from 0.7.0; fixed in 0.8.14
- @xmldom/xmldom (npm): affected from 0.9.0; fixed in 0.9.11
- @xmldom/xmldom (npm): affected from 0.9.0; fixed in 0.9.11
- xmldom (npm): affected all versions up to 0.6.0; no fix listed
- xmldom (npm): affected all versions up to 0.6.0; no fix listed

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

## Sources

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

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