CVE-2026-83607
xmldom XMLSerializer allows attacker-controlled tag names to inject XML/HTML, enabling XSS.
Is CVE-2026-83607 being exploited?
Not confirmed. CVE-2026-83607 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-83607?
CVE-2026-83607 is rated High. 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-83607?
Yes. A fix has been recorded for CVE-2026-83607. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-83607 affect?
CVE-2026-83607 affects @xmldom/xmldom <=0.8.13, @xmldom/xmldom <=0.9.10, xmldom <=0.6.0 (unfixed), Node.js apps using xmldom. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-83607?
Upgrade to @xmldom/xmldom 0.8.14 or 0.9.11; replace/unmaintained xmldom variants and sanitize inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-controlled tag names can inject attributes/elements/processing instructions into serialized XML/HTML, leading to cross-site scripting in browsers.
Immediate action required
- affected<= 0.6.0
- affected>= 0.7.0 and < 0.8.14
- affected>= 0.9.0 and < 0.9.11
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.