CVE-2026-83605
Attribute-name injection in xmldom enables injected attributes/event handlers in serialized XML.
Is CVE-2026-83605 being exploited?
Not confirmed. CVE-2026-83605 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-83605?
CVE-2026-83605 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-83605?
Yes. A fix has been recorded for CVE-2026-83605. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-83605 affect?
CVE-2026-83605 affects @xmldom/xmldom versions before 0.8.14 and before 0.9.11, xmldom version 0.6.0 and earlier, Node.js/web apps using xmldom. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-83605?
Upgrade to @xmldom/xmldom 0.8.14 or 0.9.11; replace or isolate legacy xmldom.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted attribute names can inject additional attributes (including event handlers) into serialized XML consumed by browsers, enabling DOM XSS.
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.