CVE-2026-83607

published 1 Sep 2026 · updated 6 Sep 2026

xmldom: Element name injection via createElement() bypasses requireWellFormed

8.7HighCVSS 8.7EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
xmldom>=0.7.0 <0.8.14, >=0.9.0 <0.9.11, <=0.6.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-83607 severity on Zeptric[![CVE-2026-83607](https://zeptric.io/badge/cve/CVE-2026-83607.svg)](https://zeptric.io/cve/CVE-2026-83607)