Improper Encoding or Escaping of Output Affecting @xmldom/xmldom package, versions >=0.7.0 <0.8.15>=0.9.0-beta.1 <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-19499074
- published2 Sept 2026
- disclosed1 Sept 2026
- creditDerin Rausch
Introduced: 1 Sep 2026
NewCVE-2026-83610 (opens in a new tab)How to fix?
Upgrade @xmldom/xmldom to version 0.8.15, 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 Improper Encoding or Escaping of Output in the serializeToString function. An attacker can inject arbitrary XML markup by creating an EntityReference node with an invalid nodeName and directly serializing it with requireWellFormed: true.
Note: This is only exploitable if the application explicitly creates and serializes an EntityReference node, as the parser does not generate these nodes by default and element-child insertion is rejected.