CVE-2026-83618
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.10 until 0.9.12, the requireWellFormed: true serializer validates DocumentType.publicId and DocumentType.systemId with PubidLiteral_match and SystemLiteral_match expressions produced by reg() in lib/grammar.js, which inherit the multiline flag. A complete valid literal on the first line can therefore satisfy the matcher while U+000A, U+000D, U+2028, or U+2029 and breakout markup remain in the emitted <!DOCTYPE ...> declaration. This bypasses the strict-serialization mitigation for the earlier DocumentType injection advisory; creation and direct property assignment remain unvalidated by design. 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-vr34-hp96-76pp
- nvd.nist.gov/vuln/detail/CVE-2026-83618
- github.com/advisories/GHSA-vr34-hp96-76pp
- nvd.nist.gov/vuln/detail/CVE-2026-83618
- cve.org/CVERecord?id=CVE-2026-83618
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.