XML Injection Affecting node-xmldom package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.57% (45th percentile)

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-ECHOLATEST-NODEXMLDOM-19498292
  • published2 Sept 2026
  • disclosed1 Sept 2026

Introduced: 1 Sep 2026

CVE-2026-83618  (opens in a new tab)
CWE-91  (opens in a new tab)
CWE-625  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest node-xmldom.

NVD Description

Note: Versions mentioned in the description apply only to the upstream node-xmldom package and not the node-xmldom package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1