Skip to content
Web

CVE-2026-83616

8.7
High
EPSS 0.35%Patch availableSep 2, 2026

XML processing-instruction injection in xmldom allows crafted XML structure injection.

common questions

Is CVE-2026-83616 being exploited?

Not confirmed. CVE-2026-83616 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-83616?

CVE-2026-83616 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-83616?

Yes. A fix has been recorded for CVE-2026-83616. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-83616 affect?

CVE-2026-83616 affects @xmldom/xmldom < 0.8.15, @xmldom/xmldom < 0.9.12, xmldom 0.6.0 and earlier, 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-83616?

Upgrade to @xmldom/xmldom 0.8.15 or 0.9.12; sanitize inputs if unpatchable.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
@xmldom/xmldom < 0.8.15@xmldom/xmldom < 0.9.12xmldom 0.6.0 and earlierNode.js apps using xmldom
impact

An attacker can craft a processing-instruction target to inject XML structure during serialization, enabling XML injection, data manipulation, or downstream XML parsing issues (CWE-91).

action required

Patch when possible

affected versions
xmldom xmldom
  • affected<= 0.6.0
@xmldom xmldom
  • 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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free