Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.7amended

xmldom: Uncontrolled recursion in XML serialization leads to DoS

CVE-2026-41673GHSA-2v35-w6hq-6mfw

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.8.13>= 0.9.0, < 0.9.10
    Fixed in
    0.8.13, 0.9.10

  • 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 4.0
8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-41673: 0.64% estimated exploitation activity in the next 30 days; percentile 50.86 (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.

Summary Seven recursive traversals in lib/dom.js operate without a depth limit. A sufficiently deeply nested DOM tree causes a RangeError: Maximum call stack size exceeded, crashing the application. Reported operations: - Node.prototype.normalize() — reported by @praveen-kv (email 2026-04-05) and @KarimTantawey (GHSA-fwmp-8wwc-qhv6, via DOMParser.parseFromString()) - XMLSerializer.serializeToString() — reported by @Jvr2022 (GHSA-2v35-w6hq-6mfw) and @KarimTantawey (GHSA-j2hf-fqwf-rrjf) Additionally, discovered in research: - Element.getElementsByTagName() / getElementsByTagNameNS() / getElementsByClassName() / getElementById() - Node.cloneNode(true) - Document.importNode(node, true) - node.textContent (getter) - Node.isEqualNode(other) All seven share the same root cause: pure-JavaScript recursive tree traversal with no depth guard. A single deeply nested document (parsed successfully) triggers any or all of these operations. --- Details Root cause lib/dom.js implements DOM tree…

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

    Amended from ghsa record GHSA-2v35-w6hq-6mfw

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-2v35-w6hq-6mfw

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-2026-41673

Advisory: xmldom: Uncontrolled recursion in XML serialization leads to DoS
IDs: CVE-2026-41673, GHSA-2v35-w6hq-6mfw
Record: https://patchnext.com/advisories/cve-2026-41673 (revision 3, source checked 26 Oct 2026, 12:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
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.10, 0.8.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @xmldom/xmldom: affected < 0.8.13; >= 0.9.0, < 0.9.10; fixed in 0.8.13, 0.9.10
- 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-2v35-w6hq-6mfw (OSV record GHSA-2v35-w6hq-6mfw lists affected ranges: npm @xmldom/xmldom >=0 =0.9.0 =0 <=0.6.0)
- Verified: https://github.com/advisories/GHSA-2v35-w6hq-6mfw (GitHub-reviewed advisory GHSA-2v35-w6hq-6mfw lists affected ranges: npm @xmldom/xmldom >=0 =0.9.0 =0 <=0.6.0)

Commands are suggestions: review each one before running it.

Loading voting…