Bug 2526820 (CVE-2026-83610) - CVE-2026-83610 xmldom: @xmldom/xmldom: xmldom: XML fragment injection via invalid EntityReference serialization
Summary: CVE-2026-83610 xmldom: @xmldom/xmldom: xmldom: XML fragment injection via inv...
Keywords:
Status: NEW
Alias: CVE-2026-83610
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2527259 2527262 2527268 2527276 2527279 2527282
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-01 14:47 UTC by OSIDB Bzimport
Modified: 2026-09-02 07:52 UTC (History)
33 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-01 14:47:55 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.