Answer in brief
CVE-2026-83608 records a High severity (CVSS 0.0) vulnerability in xmldom: DocType `name` Injection 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.9.0, < 0.9.12 || >= 0.7.0, < 0.8.15 | Not reported |
| xmldomnpm | <=0.6.0 | Not reported |
| @xmldom/xmldomnpm | >=0.9.0,<=0.9.11 | 0.9.12 |
| @xmldom/xmldomnpm | >=0.7.0,<=0.8.14 | 0.8.15 |
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, the DOCUMENT_TYPE_NODE branch in lib/dom.js validates publicId, systemId, and internalSubset under requireWellFormed: true but emits DocumentType.name verbatim. A name containing > or whitespace can terminate the <!DOCTYPE ...> declaration and inject sibling markup; the value can be supplied through createDocumentType() on the 0.8.x and unscoped lines or through a direct DocumentType.name property write on every affected line. The default path and legacy creation-time behavior remain permissive, while the vulnerable strict path fails to enforce an XML Name. 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.