Answer in brief
CVE-2026-83610 records a Medium severity (CVSS 0.0) vulnerability in xmldom: XML fragment injection via invalid EntityReference.nodeName during requireWellFormed serialization. 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.15 || >= 0.9.0, < 0.9.12 | Not reported |
| xmldomnpm | <=0.6.0 | Not reported |
| @xmldom/xmldomnpm | >=0.7.0,<=0.8.14 | 0.8.15 |
| @xmldom/xmldomnpm | >=0.9.0,<=0.9.11 | 0.9.12 |
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.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, Document.createEntityReference(name) accepts an invalid name and the ENTITY_REFERENCE_NODE serializer emits the resulting nodeName directly in &name; form. Directly serializing the node or fragment with XMLSerializer.serializeToString() and requireWellFormed: true can therefore break the entity-reference boundary and produce attacker-controlled XML markup when reparsed. The parser does not ordinarily create these nodes, and element-child insertion is rejected, so exploitation requires an application to create and directly serialize an EntityReference. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
Quoted source text, attributed separately from HOL analysis.