PT-2026-84251 · Npm · @Xmldom/Xmldom+1
CVE-2026-83605
·
Published
2026-08-12
·
Updated
2026-09-09
CVSS v4.0
8.7
High
| Vector | AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Name of the Vulnerable Software and Affected Versions
@xmldom/xmldom versions prior to 0.8.14
@xmldom/xmldom versions prior to 0.9.11
xmldom versions 0.6.0 and earlier
Description
The
Element.setAttribute() function calls the private createAttribute(name) path without validating the attribute name. Because XMLSerializer.serializeToString() emits attribute names verbatim and the requireWellFormed: true setting does not validate them, a crafted name can terminate the intended attribute and inject additional attributes, such as event handlers, into output consumed by browsers. Synthesized xmlns:PREFIX declarations are also subject to this unchecked-name boundary.Recommendations
Update @xmldom/xmldom to version 0.8.14 or later.
Update @xmldom/xmldom to version 0.9.11 or later.
At the moment, there is no information about a newer version that contains a fix for this vulnerability.
Exploit
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
@Xmldom/Xmldom
Xmldom