CVE-2026-83618
xmldom serializer allows DocumentType injection via unvalidated line breaks in DOCTYPE.
Is CVE-2026-83618 being exploited?
Not confirmed. CVE-2026-83618 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-83618?
CVE-2026-83618 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-83618?
Yes. A fix has been recorded for CVE-2026-83618. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-83618 affect?
CVE-2026-83618 affects @xmldom/xmldom 0.9.10 - 0.9.11, Node.js applications and packages depending on xmldom. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-83618?
Upgrade to @xmldom/xmldom v0.9.12; audit and rebuild dependent packages.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Bypasses serializer validation to inject unsafe DOCTYPE content, enabling XML/DOCTYPE injection and potential XEE or downstream markup injection.
Patch when possible
- affected>= 0.9.10 and < 0.9.12
- affected>= 0.9.10 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.