CVE-2026-83614
XML DOM parser vulnerable to quadratic-time DoS via malformed tags and normalize().
Is CVE-2026-83614 being exploited?
Not confirmed. CVE-2026-83614 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.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-83614?
CVE-2026-83614 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-83614?
Yes. A fix has been recorded for CVE-2026-83614. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-83614 affect?
CVE-2026-83614 affects @xmldom/xmldom prior to 0.8.15 and 0.9.12, xmldom 0.3.0-0.6.0 (legacy, no fix). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-83614?
Upgrade @xmldom/xmldom to 0.8.15 or 0.9.12; remove/replace xmldom 0.3–0.6.0; validate/limit XML input.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Denial of Service: crafted XML or normalize() calls can trigger quadratic CPU/memory exhaustion via DOMParser.parseFromString or normalize().
Patch when possible
- affected>= 0.3.0 and <= 0.6.0
- affected>= 0.7.0 and < 0.8.15
- affected>= 0.9.0 and < 0.9.12
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.