Bug 2526817 (CVE-2026-83607) - CVE-2026-83607 xmldom: xmldom: Cross-site scripting via unvalidated element name injection
Summary: CVE-2026-83607 xmldom: xmldom: Cross-site scripting via unvalidated element n...
Keywords:
Status: NEW
Alias: CVE-2026-83607
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: 2527518 2527519 2527520 2527522 2527523 2527524 2527525 2527526
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-01 14:46 UTC by OSIDB Bzimport
Modified: 2026-09-02 15:09 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:46:07 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.14 and 0.9.11, and in xmldom version 0.6.0 and earlier, Document.createElement(tagName) stores an unvalidated element name and XMLSerializer.serializeToString() emits that name verbatim. The requireWellFormed: true path did not validate the element qualified name or synthesized xmlns:PREFIX declaration, so attacker-controlled tag names could inject attributes, elements, or processing instructions into serialized XML or HTML and could cause cross-site scripting when browser-consumed. The unchecked values violate the XML QName constraint, and default serialization and creation-time createElement() behavior remain permissive. This issue is fixed in @xmldom/xmldom versions 0.8.14 and 0.9.11; no fixed version is available for xmldom.
Note You need to log in before you can comment on or make changes to this bug.