CVE-2026-83606
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.0-beta.9 until 0.9.11, the processing-instruction production in lib/grammar.js lets the greedy S+ separator and lazy Char*? data group repeatedly repartition a long whitespace tail when the required closing ?> is absent. Both parsePI and parseProcessingInstruction apply the expression to the entire remaining source, causing quadratic backtracking during DOMParser.parseFromString() under default options and allowing a small unauthenticated XML input to stall the Node.js event loop. This issue is fixed in @xmldom/xmldom version 0.9.11.
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/73df6b8bdbd86f904b9e8c3ab9c49aa54ef2802e
- github.com/xmldom/xmldom/pull/1039
- github.com/xmldom/xmldom/releases/tag/0.9.11
- github.com/xmldom/xmldom/security/advisories/GHSA-g53g-w8rj-fmg7
- nvd.nist.gov/vuln/detail/CVE-2026-83606
- github.com/advisories/GHSA-g53g-w8rj-fmg7
- nvd.nist.gov/vuln/detail/CVE-2026-83606
- cve.org/CVERecord?id=CVE-2026-83606
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.