CVE-2026-83617
xmldom validation bypass allows newline-based markup injection in element/attribute names.
Is CVE-2026-83617 being exploited?
Not confirmed. CVE-2026-83617 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.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-83617?
CVE-2026-83617 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-83617?
Yes. A fix has been recorded for CVE-2026-83617. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-83617 affect?
CVE-2026-83617 affects @xmldom/xmldom >=0.9.11 <0.9.12, Node.js applications and libraries bundling xmldom. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-83617?
Upgrade to @xmldom/xmldom v0.9.12 immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted XML names with newline bypass validation, enabling markup/attribute injection and document-structure manipulation; can lead to XSS or parser confusion.
Patch when possible
- affected>= 0.9.11 and < 0.9.12
- affected>= 0.9.11 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.