CVE-2022-39353 | xmldom allows multiple root nodes in a DOM

Exp

xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) `DOMParser` and `XMLSerializer` module. xmldom parses XML that is not well-formed because it contains multiple top level elements, and adds all root nodes to the `childNodes` collection of the `Document`, without reporting any error or throwing. This breaks the assumption that there is only a single root node in the tree, which led to issuance of CVE-2022-39299 as it is a potential issue for dependents. Update to @xmldom/xmldom@~0.7.7, @xmldom/xmldom@~0.8.4 (dist-tag latest) or @xmldom/xmldom@>=0.9.0-beta.4 (dist-tag next). As a workaround, please one of the following approaches depending on your use case: instead of searching for elements in the whole DOM, only search in the `documentElement`or reject a document with a document that has more then 1 `childNode`.

Published: 2022-11-02 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-39353 is rated High Exploit Risk (79/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 0.97%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-39353

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-39353

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-27 1.31% 0.97% -0.34%
2 2025-11-21 0.75% 1.31% +0.57%
3 2025-11-18 — 0.75% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-39353

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.4 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.5 [email protected]
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2022-39353

GitHub Security Advisory for CVE-2022-39353

GHSA-crh6-fp67-6883 · Severity: critical · Ecosystem: npm — xmldom allows multiple root nodes in a DOM

OS Trackers for CVE-2022-39353

vendor priority summary link
debian not yet assigned CVE-2022-39353 not yet assigned priority: Debian including 1 source packages (node-xmldom), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-39353
redhat high — https://access.redhat.com/security/cve/CVE-2022-39353
ubuntu medium CVE-2022-39353 medium priority: Ubuntu including 1 source packages (node-xmldom), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 5, needs-triage 3, released 3, DNE 1, not-affected 1. https://ubuntu.com/security/CVE-2022-39353

Affected software / configurations for CVE-2022-39353

Vendor Product Version Raw CPE
xmldom_project xmldom < 0.6.0 cpe:2.3:a:xmldom_project:xmldom:*:*:*:*:*:node.js:*:*
xmldom_project xmldom >= 0.7.0, < 0.7.7 cpe:2.3:a:xmldom_project:xmldom:*:*:*:*:*:node.js:*:*
xmldom_project xmldom >= 0.8.0, < 0.8.4 cpe:2.3:a:xmldom_project:xmldom:*:*:*:*:*:node.js:*:*
xmldom_project xmldom 0.9.0 cpe:2.3:a:xmldom_project:xmldom:0.9.0:beta1:*:*:*:node.js:*:*
xmldom_project xmldom 0.9.0 cpe:2.3:a:xmldom_project:xmldom:0.9.0:beta2:*:*:*:node.js:*:*
xmldom_project xmldom 0.9.0 cpe:2.3:a:xmldom_project:xmldom:0.9.0:beta3:*:*:*:node.js:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2022-39353

cvelogic Threat Intelligence