CVE-2022-39353

CRITICALNVD 9.49.4—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under NVD CVSS v3. EPSS exploit probability: 1.2%, top 36% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.4Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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 documentElementor reject a document with a document that has more then 1 childNode.

CVSS v3
9.4
EG Score
9.4(medium)
EG Risk
73(Attend)
EG Risk 73/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity94% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
65%
KEV
Not listed

Published

November 2, 2022

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Jul 15, 2026
Patch available. Sources: github.
generic Patch Available

[SECURITY] [DLA 3260-1] node-xmldom security update

https://lists.debian.org/debian-lts-announce/2023/01/msg00000.html
github Patch Available

Allows multiple root elements in a DOM tree · Advisory · xmldom/xmldom · GitHub

https://github.com/xmldom/xmldom/security/advisories/GHSA-crh6-fp67-6883
generic

Missing error for XML documents with multiple root element nodes · Issue #150 · jindw/xmldom · GitHub

https://github.com/jindw/xmldom/issues/150

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunode-xmldom (0.7.5-1ubuntu0.22.04.1) @ jammy2026-05-25ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFixed inDependents
xmldom———
@xmldom/xmldom—0.9.0-beta.4—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 13× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 116 total refreshes for this CVE.

  1. 2026-07-26 14:52 UTCEPSS rescore
  2. 2026-07-25 14:15 UTCEPSS rescore
  3. 2026-07-25 14:15 UTCEPSS rescore
  4. 2026-07-24 14:15 UTCEPSS rescore
  5. 2026-07-24 14:15 UTCEPSS rescore
  6. 2026-07-23 14:16 UTCEPSS rescore
  7. 2026-07-23 02:13 UTCEG score recompute
  8. 2026-07-22 23:00 UTCEG score recompute
  9. 2026-07-22 14:06 UTCEPSS rescore
  10. 2026-07-22 14:06 UTCEPSS rescore
  11. 2026-07-21 15:23 UTCEPSS rescore
  12. 2026-07-21 15:22 UTCEPSS rescore
  13. 2026-07-20 17:05 UTCEPSS rescore
  14. 2026-07-19 14:29 UTCEPSS rescore
  15. 2026-07-19 02:27 UTCEPSS rescore
  16. 2026-07-19 02:27 UTCEPSS rescore
  17. 2026-07-18 10:03 UTCEPSS rescore
  18. 2026-07-18 10:03 UTCEPSS rescore
  19. 2026-07-16 17:00 UTCEPSS rescore
  20. 2026-07-16 16:19 UTCOSV refresh
  21. 2026-07-15 16:56 UTCEPSS rescore
  22. 2026-07-15 16:56 UTCEPSS rescore
  23. 2026-07-15 01:58 UTCEPSS rescore
  24. 2026-07-15 01:58 UTCEPSS rescore
  25. 2026-07-13 22:28 UTCEPSS rescore
Show 75 more
  1. 2026-07-13 22:28 UTCEPSS rescore
  2. 2026-07-13 06:11 UTCEPSS rescore
  3. 2026-07-13 06:11 UTCEPSS rescore
  4. 2026-07-12 05:44 UTCEPSS rescore
  5. 2026-07-12 05:44 UTCEPSS rescore
  6. 2026-07-11 08:25 UTCEPSS rescore
  7. 2026-07-09 19:08 UTCEPSS rescore
  8. 2026-07-08 15:12 UTCEPSS rescore
  9. 2026-07-07 13:44 UTCEPSS rescore
  10. 2026-07-06 16:25 UTCEPSS rescore
  11. 2026-07-06 16:25 UTCEPSS rescore
  12. 2026-07-06 02:21 UTCEPSS rescore
  13. 2026-07-06 02:21 UTCEPSS rescore
  14. 2026-07-05 02:28 UTCEPSS rescore
  15. 2026-07-04 06:29 UTCEPSS rescore
  16. 2026-07-04 06:29 UTCEPSS rescore
  17. 2026-07-01 15:04 UTCEPSS rescore
  18. 2026-06-30 23:20 UTCEPSS rescore
  19. 2026-06-30 23:20 UTCEPSS rescore
  20. 2026-06-29 14:04 UTCEPSS rescore
  21. 2026-06-28 14:32 UTCOSV refresh
  22. 2026-06-28 14:06 UTCEPSS rescore
  23. 2026-06-28 04:54 UTCEPSS rescore
  24. 2026-06-28 04:54 UTCEPSS rescore
  25. 2026-06-27 03:07 UTCEPSS rescore
  26. 2026-06-27 03:07 UTCEPSS rescore
  27. 2026-06-25 13:48 UTCEPSS rescore
  28. 2026-06-25 13:48 UTCEPSS rescore
  29. 2026-06-24 14:03 UTCEPSS rescore
  30. 2026-06-24 14:03 UTCEPSS rescore
  31. 2026-06-23 21:31 UTCEPSS rescore
  32. 2026-06-23 21:31 UTCEPSS rescore
  33. 2026-06-22 14:24 UTCEPSS rescore
  34. 2026-06-22 14:24 UTCEPSS rescore
  35. 2026-06-21 14:55 UTCEPSS rescore
  36. 2026-06-21 14:55 UTCEPSS rescore
  37. 2026-06-21 01:58 UTCEPSS rescore
  38. 2026-06-21 01:58 UTCEPSS rescore
  39. 2026-06-19 19:24 UTCEPSS rescore
  40. 2026-06-19 19:24 UTCEPSS rescore
  41. 2026-06-18 17:51 UTCEPSS rescore
  42. 2026-06-18 17:51 UTCEPSS rescore
  43. 2026-06-17 17:51 UTCEPSS rescore
  44. 2026-06-17 17:51 UTCEPSS rescore
  45. 2026-06-16 17:51 UTCEPSS rescore
  46. 2026-06-15 17:46 UTCEPSS rescore
  47. 2026-06-14 23:15 UTCEPSS rescore
  48. 2026-06-13 22:58 UTCEPSS rescore
  49. 2026-06-12 23:10 UTCEPSS rescore
  50. 2026-06-12 23:10 UTCEPSS rescore
  51. 2026-06-11 13:58 UTCEPSS rescore
  52. 2026-06-11 13:58 UTCEPSS rescore
  53. 2026-06-11 03:09 UTCOSV refresh
  54. 2026-06-10 22:17 UTCEPSS rescore
  55. 2026-06-10 13:20 UTCEPSS rescore
  56. 2026-06-08 14:15 UTCEPSS rescore
  57. 2026-06-08 14:15 UTCEPSS rescore
  58. 2026-06-07 15:23 UTCEPSS rescore
  59. 2026-06-07 15:23 UTCEPSS rescore
  60. 2026-06-06 13:46 UTCEPSS rescore
  61. 2026-06-06 13:46 UTCEPSS rescore
  62. 2026-06-06 13:46 UTCEPSS rescore
  63. 2026-06-05 22:46 UTCEPSS rescore
  64. 2026-06-05 22:45 UTCEPSS rescore
  65. 2026-06-05 06:09 UTCEPSS rescore
  66. 2026-06-05 06:09 UTCEPSS rescore
  67. 2026-06-04 13:11 UTCEPSS rescore
  68. 2026-06-04 13:11 UTCEPSS rescore
  69. 2026-06-02 20:11 UTCEPSS rescore
  70. 2026-06-02 20:11 UTCEPSS rescore
  71. 2026-06-01 13:50 UTCEPSS rescore
  72. 2026-06-01 13:50 UTCEPSS rescore
  73. 2026-05-31 22:29 UTCEPSS rescore
  74. 2026-05-31 22:29 UTCEPSS rescore
  75. 2026-05-31 22:29 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-39353?
CVE-2022-39353 is a critical vulnerability published on November 2, 2022. 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…
When was CVE-2022-39353 disclosed?
CVE-2022-39353 was first published in the National Vulnerability Database on November 2, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-39353 actively exploited?
CVE-2022-39353 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 35.5% of all scored CVEs.
What is the CVSS score of CVE-2022-39353?
CVE-2022-39353 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2022-39353?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-39353, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-39353

Explore →

Is Your Infrastructure Affected by CVE-2022-39353?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs