Bug 2526858 (CVE-2026-83616) - CVE-2026-83616 xmldom: xmldom: XML Structure Injection via Unvalidated Processing Instruction Targets
Summary: CVE-2026-83616 xmldom: xmldom: XML Structure Injection via Unvalidated Proces...
Keywords:
Status: NEW
Alias: CVE-2026-83616
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2528030 2528031 2528033 2528034 2528035 2528036 2528029 2528032
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-01 15:15 UTC by OSIDB Bzimport
Modified: 2026-09-03 13:59 UTC (History)
33 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-01 15:15:45 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.createProcessingInstruction(target, data) in lib/dom.js accepts an unvalidated target, while the requireWellFormed: true serializer checks only for a colon and the reserved case-insensitive xml name on 0.9.x and performs no target check on 0.8.x. Because serialization emits <?target data?>, a target containing >, ?, whitespace, or another invalid XML-name character can break the processing-instruction boundary and inject XML structure. 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.