CVE-2026-83610
Received Received - Intake

XML External Entity Injection in xmldom

Publication date: 2026-09-01

Last updated on: 2026-09-01

Assigner: GitHub, Inc.

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.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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-01
Last Modified
2026-09-01
Generated
2026-09-01
AI Q&A
2026-09-01
EPSS Evaluated
N/A
NVD
CVE-2026-83610
EUVD
EUVD-2026-69222

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
@xmldom xmldom From 0.8.15 (inc) to 0.9.12 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-116 The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the xmldom library, which is used for parsing and serializing XML in JavaScript. The issue is in the Document.createEntityReference function, which can accept invalid names and then serialize them in a way that breaks XML structure boundaries. This allows attacker-controlled XML markup to be injected when the XML is reparsed.

Detection Guidance

This vulnerability requires checking if your application uses vulnerable versions of xmldom (0.6.0 or earlier, or @xmldom/xmldom before 0.8.15 and 0.9.12). Inspect package.json or dependency files for xmldom versions. No direct network detection commands are provided as this is a library-level issue.

Impact Analysis

If your application uses the affected xmldom versions and creates or serializes EntityReference nodes, an attacker could craft malicious XML input that bypasses security controls. This could lead to XML injection attacks, data corruption, or other unintended behavior when the XML is processed.

Compliance Impact

This vulnerability could potentially affect compliance with GDPR and HIPAA by enabling XML injection attacks. If exploited, it may allow unauthorized data access or manipulation, violating data integrity and confidentiality requirements under these regulations.

Mitigation Strategies

Upgrade to patched versions: @xmldom/xmldom 0.8.15 or 0.9.12. If using xmldom 0.6.0 or earlier, migrate to a supported version. Avoid creating and serializing EntityReference nodes in applications.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-83610. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart