CVE-2026-83616Public exploitNetwork attack vectorHinoki check available

XML injection via unvalidated processing-instruction target

Published Sep 1, 2026 · Updated Sep 1, 2026

XML injection in xmldom allows attackers to alter serialized XML output through a crafted processing-instruction target value. Document.createProcessingInstruction(target, data) in lib/dom.js stores the target without validating it as an XML NCName, and XMLSerializer emits it verbatim while requireWellFormed performs only incomplete checks. Exploitation requires an application to place attacker-controlled text in a processing-instruction target and serialize it; boundary-breaking characters can inject elements, text, or additional instructions into downstream XML.

CVSS severity8.7
High
EPSS probability0.35%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

XML injection in xmldom allows attackers to alter serialized XML output through a crafted processing-instruction target value. Document.createProcessingInstruction(target, data) in lib/dom.js stores the target without validating it as an XML NCName, and XMLSerializer emits it verbatim while requireWellFormed performs only incomplete checks. Exploitation requires an application to place attacker-controlled text in a processing-instruction target and serialize it; boundary-breaking characters can inject elements, text, or additional instructions into downstream XML.

The record

CVE
CVE-2026-83616
Published
Sep 1, 2026
Updated
Sep 1, 2026
Vendor
xmldom
Product
xmldom
Classifications
CWE-91
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 1, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 1, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=<= 0.6.0
  2. Affected versionversion=>= 0.7.0, < 0.8.15
  3. Affected versionversion=>= 0.9.0, < 0.9.12

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

xmldom · xmldomversion=<= 0.6.0; version=>= 0.7.0, < 0.8.15; version=>= 0.9.0, < 0.9.12

Published CVSS scores

8.7GitHub CNACVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-91XML Injection (aka Blind XPath Injection)

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo