LiveActive security incident?Get immediate response
CVE Record

CVE-2026-41673: xmldom: Denial of service via uncontrolled recursion in XML serialization

xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) `DOMParser` and `XMLSerializer` module. In @xmldom/xmldom prior to versions 0.9.10 and 0.8.13 and xmldom version 0.6.0 and prior, 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. This issue has been patched in versions @xmldom/xmldom versions 0.9.10 and 0.8.13.

HighCVSS 8.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-41673 lets deeply nested XML data crash applications using vulnerable xmldom serialization code. The business impact is service disruption, not data theft. Risk is highest where internet-facing services parse or serialize attacker-controlled XML or DOM content.

Executive priority

Prioritize remediation for externally reachable services and ingestion pipelines processing XML. Treat as a high availability risk; schedule normal emergency handling only if critical services accept untrusted XML today.

Technical view

Affected xmldom code performs seven recursive traversals in lib/dom.js without a depth limit. A sufficiently deep DOM tree can trigger RangeError: Maximum call stack size exceeded and crash the application. Fixed @xmldom/xmldom releases are 0.8.13 and 0.9.10.

Likely exposure

Node.js or JavaScript applications using xmldom <=0.6.0, @xmldom/xmldom <0.8.13, or @xmldom/xmldom 0.9.0-0.9.9 are exposed, especially when XML or DOM content can be influenced remotely.

Exploitation context

The CVSS vector indicates network attackability, low complexity, no privileges, and no user interaction. The provided sources do not show known active exploitation, and KEV is false. Evidence supports denial of service only.

Researcher notes

Focus review on dependency reachability, not just package presence. The issue requires a deeply nested DOM reaching vulnerable serialization traversal. Sources name no confidentiality or integrity impact and no public exploitation evidence.

Mitigation direction

  • Upgrade @xmldom/xmldom to 0.8.13 or 0.9.10 where used.
  • Identify and address legacy xmldom <=0.6.0 per vendor guidance.
  • Reduce acceptance of deeply nested untrusted XML where feasible.
  • Use dependency management to prevent reintroduction of affected versions.

Validation and detection

  • Inventory direct and transitive dependencies for xmldom and @xmldom/xmldom versions.
  • Confirm resolved versions are @xmldom/xmldom 0.8.13, 0.9.10, or later.
  • Review code paths using DOMParser or XMLSerializer with untrusted input.
  • Verify production crash monitoring covers XML processing services.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-674: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-776: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-41673 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
17Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——GitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-41673Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADP@xmldom/xmldom: xmldom: xmldom: Denial of Service via deeply nested XML documents
other:Red Hat severity ratingcvssV3_1
  • 2026-05-07T05:02:01.500Z: Reported to Red Hat.
  • 2026-05-07T03:40:28.378Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
xmldomxmldomxmldom <= 0.6.0, @xmldom/xmldom >= 0.9.0, < 0.9.10, @xmldom/xmldom < 0.8.13Listed
Weakness

CWE details

CWE-674CWE-776

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-674 · source CWE mapping

Uncontrolled Recursion

Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs
CWE-776 · source CWE mapping

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs