XML Injection Affecting @xmldom/xmldom package, versions >=0.9.11 <0.9.12
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-XMLDOMXMLDOM-19499071
- published2 Sept 2026
- disclosed1 Sept 2026
- creditChristian Bewernitz
Introduced: 1 Sep 2026
NewCVE-2026-83617 (opens in a new tab)How to fix?
Upgrade @xmldom/xmldom to version 0.9.12 or higher.
Overview
@xmldom/xmldom is a javascript ponyfill to provide the following APIs that are present in modern browsers to other runtimes. Since version 0.7.0 this package is published to npm as @xmldom/xmldom and no longer as xmldom
Affected versions of this package are vulnerable to XML Injection via the reg() function in lib/grammar.js, which compiled all anchored name/id validation regexes with the multiline (m) flag. Because ^ and $ anchors match line boundaries rather than string boundaries when m is set, an element name, attribute name, or DOCTYPE publicId/systemId containing an ECMAScript line terminator (U+000A, U+000D, U+2028, U+2029) passes validation as long as its first line is conformant, allowing arbitrary trailing markup to bypass well-formedness checks. An attacker who can supply such values can inject content that serializeToString emits without raising InvalidStateError, and createElementNS, createAttributeNS, createDocumentType, and createAttribute accept without raising InvalidCharacterError.
Note: This is only exploitable when { requireWellFormed: true } is explicitly passed to serializeToString, or when the application relies on the DOM creation APIs to enforce name validity.