CVE-2026-83617
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 …
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.11 until 0.9.12, the requireWellFormed: true element and attribute name checks use the anchored QName_exact expression produced by reg() in lib/grammar.js, which inherits the multiline flag. A name with a valid first line followed by U+000A, U+000D, U+2028, or U+2029 and breakout markup therefore passes validation and is emitted verbatim in element start and end tags or attribute names. This bypasses the strict-serialization checks introduced for the earlier element-name and attribute-name injection advisories, while the default serialization path remains outside the strict guarantee. This issue is fixed in @xmldom/xmldom version 0.9.12.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/xmldom/xmldom/commit/7b2ec67e1750daadd0bb06c92e875e726544a362
- github.com/xmldom/xmldom/pull/1071
- github.com/xmldom/xmldom/releases/tag/0.9.12
- github.com/xmldom/xmldom/security/advisories/GHSA-jxjr-3g7g-3944
- nvd.nist.gov/vuln/detail/CVE-2026-83617
- github.com/advisories/GHSA-jxjr-3g7g-3944
- nvd.nist.gov/vuln/detail/CVE-2026-83617
- cve.org/CVERecord?id=CVE-2026-83617
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.