Node xmldom: 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… (CVE-2026-83610)
Description
A vulnerability in node-xmldom versions prior to @xmldom/xmldom 0.8.15 and 0.9.12, and in xmldom 0.6.0 and earlier, allows Document.createEntityReference(name) to accept invalid names. This leads to serialization of attacker-controlled XML markup when using XMLSerializer.serializeToString() with requireWellFormed: true. Exploitation requires an application to create and serialize an EntityReference node directly. Fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fix is available for xmldom.
CVSS v4.0
Affected software
pkg:deb/ubuntu/node-xmldom?arch=source&distro=focalpkg:deb/ubuntu/node-xmldom?arch=source&distro=jammypkg:deb/ubuntu/node-xmldom?arch=source&distro=noblepkg:deb/ubuntu/node-xmldom?arch=source&distro=stonkingpkg:deb/ubuntu/node-xmldom?arch=source&distro=resoluteRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The node-xmldom library, a JavaScript XML DOM parser and serializer, has a vulnerability in versions prior to @xmldom/xmldom 0.8.15 and 0.9.12, and in xmldom 0.6.0 and earlier. The Document.createEntityReference(name) method accepts invalid entity names, and the ENTITY_REFERENCE_NODE serializer emits the nodeName directly in &name; form. When serialized with XMLSerializer.serializeToString() using requireWellFormed: true, this can break the entity-reference boundary and produce attacker-controlled XML markup upon reparsing. The parser normally does not create these nodes, and element-child insertion is rejected, so exploitation requires an application to explicitly create and serialize an EntityReference node. The issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version exists for xmldom.
Potential Impact
An attacker can craft XML that, when serialized and reparsed, results in attacker-controlled XML markup due to improper handling of entity references. This could potentially lead to XML injection or manipulation in applications that create and serialize EntityReference nodes directly. However, exploitation requires specific application behavior, limiting the impact.
Mitigation Recommendations
Upgrade to @xmldom/xmldom versions 0.8.15 or 0.9.12 where the vulnerability is fixed. For xmldom, no fixed version is currently available, so avoid using Document.createEntityReference with untrusted input or avoid serializing EntityReference nodes. Monitor vendor advisories for updates regarding xmldom.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- UBUNTU-CVE-2026-83610
- Osv Schema Version
- 1.7.0
- Ecosystems
- ["Ubuntu:20.04:LTS","Ubuntu:22.04:LTS","Ubuntu:24.04:LTS","Ubuntu:26.10","Ubuntu:26.04:LTS"]
- Cvss Version
- 4.0
Threat ID: 6ad3f55e2cdf04f65666181c
Added to database: 10/17/2026, 22:23:26 UTC
Last enriched: 10/17/2026, 23:30:36 UTC
Last updated: 10/17/2026, 23:30:36 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.