Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8amended

xmldom allows multiple root nodes in a DOM

CVE-2022-39353GHSA-crh6-fp67-6883

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm @xmldom/xmldom

    Affected
    < 0.7.7>= 0.8.0, < 0.8.4>= 0.9.0-beta.1, < 0.9.0-beta.4
    Fixed in
    0.7.7, 0.8.4, 0.9.0-beta.4

  • npm xmldom

    Affected
    <= 0.6.0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2022-39353: 1.56% estimated exploitation activity in the next 30 days; percentile 75.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact 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 https://nvd.nist.gov/vuln/detail/CVE-2022-39299 and is a potential issue for dependents. Patches 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). Workarounds One of the following approaches might help, depending on your use case: - Instead of searching for elements in the whole DOM, only search in the documentElement. - Reject a document with a document that has more then 1 childNode. References - https://nvd.nist.gov/vuln/detail/CVE-2022-39299 - https://github.com/jindw/xmldom/issues/150 For more information If you have any questions or comments about this advisory: Email us at security@xmldom.org

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-crh6-fp67-6883

  2. Revision 1 · created ·

    Published from osv record GHSA-crh6-fp67-6883

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-39353

Advisory: xmldom allows multiple root nodes in a DOM
IDs: CVE-2022-39353, GHSA-crh6-fp67-6883
Record: https://patchnext.com/advisories/cve-2022-39353 (revision 2, source checked 26 Oct 2026, 12:21 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: @xmldom/xmldom 0.9.0-beta.4, 0.8.4, 0.7.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @xmldom/xmldom: affected < 0.7.7; >= 0.8.0, < 0.8.4; >= 0.9.0-beta.1, < 0.9.0-beta.4; fixed in 0.7.7, 0.8.4, 0.9.0-beta.4
- npm xmldom: affected <= 0.6.0

## Suggested inspection (read-only)
- `npm ls @xmldom/xmldom --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `npm ls xmldom --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @xmldom/xmldom, xmldom.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-crh6-fp67-6883 (OSV record GHSA-crh6-fp67-6883 lists affected ranges: npm xmldom >=0 =0 =0.8.0 =0.9.0-beta.1 <0.9.0-beta.4 (fixed))
- Verified: https://github.com/advisories/GHSA-crh6-fp67-6883 (GitHub-reviewed advisory GHSA-crh6-fp67-6883 lists affected ranges: npm xmldom >=0 =0 =0.8.0 =0.9.0-beta.1 <0.9.0-beta.4)

Commands are suggestions: review each one before running it.

Loading voting…