XML injection via unvalidated EntityReference name serialization
Published Sep 1, 2026 · Updated Sep 3, 2026
XML injection in affected xmldom releases allows attackers to insert XML markup through a crafted EntityReference name. Document.createEntityReference accepts an invalid name, and the ENTITY_REFERENCE_NODE serializer emits nodeName directly between an ampersand and semicolon without escaping, even when requireWellFormed is true. Exploitation requires an application to create the node from attacker input, serialize the node or fragment directly, and reparse the output; ordinary parsing does not create these nodes, and element-child insertion is rejected.
Summary
What happened
XML injection in affected xmldom releases allows attackers to insert XML markup through a crafted EntityReference name. Document.createEntityReference accepts an invalid name, and the ENTITY_REFERENCE_NODE serializer emits nodeName directly between an ampersand and semicolon without escaping, even when requireWellFormed is true. Exploitation requires an application to create the node from attacker input, serialize the node or fragment directly, and reparse the output; ordinary parsing does not create these nodes, and element-child insertion is rejected.
The record
- CVE
- CVE-2026-83610
- Published
- Sep 1, 2026
- Updated
- Sep 3, 2026
- Vendor
- xmldom
- Product
- xmldom
- Classifications
- CWE-116
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 1, 2026CVE publishedPublication date reported by the CVE source.
- Sep 3, 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.
- Affected versionversion=<= 0.6.0
- Affected versionversion=>= 0.7.0, < 0.8.15
- Affected versionversion=>= 0.9.0, < 0.9.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
Public exploit references
- Upstream EntityReference XML injection proof of conceptproof of concept · demonstrated
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