Answer in brief
CVE-2026-83605 records a High severity (CVSS 0.0) vulnerability in xmldom: Attribute name injection via setAttribute() bypasses requireWellFormed. The current sources do not mark it as known exploited. The current feed maps xmldom/xmldom (generic), @xmldom/xmldom (generic), xmldom (npm), @xmldom/xmldom (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 0.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps xmldom/xmldom (generic), @xmldom/xmldom (generic), xmldom (npm), @xmldom/xmldom (npm) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| xmldom/xmldomgeneric | <= 0.6.0 | Not reported |
| @xmldom/xmldomgeneric | >= 0.7.0, < 0.8.14 || >= 0.9.0, < 0.9.11 | Not reported |
| xmldomnpm | <=0.6.0 | Not reported |
| @xmldom/xmldomnpm | >=0.9.0,<=0.9.10 | 0.9.11 |
| @xmldom/xmldomnpm | >=0.7.0,<=0.8.13 | 0.8.14 |
Published upstream
Sep 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 1, 2026
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.
Quoted source text, attributed separately from HOL analysis.