Skip to content
Applications

CVE-2026-83613

8.7
High
EPSS 0.34%Patch availableSep 2, 2026

XML parser flaw causes quadratic parsing and can stall Node.js event loop (DoS).

common questions

Is CVE-2026-83613 being exploited?

Not confirmed. CVE-2026-83613 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-83613?

CVE-2026-83613 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-83613?

Yes. A fix has been recorded for CVE-2026-83613. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-83613 affect?

CVE-2026-83613 affects @xmldom/xmldom (versions prior to 0.8.15 and 0.9.12), xmldom (<= 0.6.0), Node.js apps parsing untrusted XML. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-83613?

Upgrade @xmldom/xmldom to >=0.8.15 or >=0.9.12; avoid/sandbox parsing untrusted XML.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
@xmldom/xmldom (versions prior to 0.8.15 and 0.9.12)xmldom (<= 0.6.0)Node.js apps parsing untrusted XML
impact

Denial of Service: crafted XML with many attributes triggers quadratic work, consuming CPU and stalling the Node.js event loop.

action required

Patch when possible

affected versions
xmldom xmldom
  • affected<= 0.6.0
@xmldom xmldom
  • affected>= 0.9.0 and < 0.9.12
  • affected>= 0.7.0 and < 0.8.15

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free