cve.bz

CVE-2026-83610 Improper Encoding or Escaping of Output

6.3 mediumEPSS 0.6%Fix available

Medium (6.3). EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in @xmldom/xmldom 0.8.15, 0.9.12.

On this page
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, Document.createEntityReference(name) accepts an invalid name and the ENTITY_REFERENCE_NODE serializer emits the resulting nodeName directly in &name; form. Directly serializing the node or fragment with XMLSerializer.serializeToString() and requireWellFormed: true can therefore break the entity-reference boundary and produce attacker-controlled XML markup when reparsed. The parser does not ordinarily create these nodes, and element-child insertion is rejected, so exploitation requires an application to create and directly serialize an EntityReference. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.

Severity

CVSS 4.0

6.3 medium
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 49th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-09-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-116 Improper Encoding or Escaping of Output
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-83610 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-83610?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-83610?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-83610 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
xmldom<= 0.6.0
@xmldom xmldom>= 0.7.0, < 0.8.15
@xmldom xmldom>= 0.9.0, < 0.9.12

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6gmq-8vp8-gcm6npm@xmldom/xmldom>=0.7.0 <0.8.150.8.15
GHSA-6gmq-8vp8-gcm6npm@xmldom/xmldom>=0.9.0 <0.9.120.9.12
GHSA-6gmq-8vp8-gcm6npmxmldom<=0.6.0no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13node-xmldomno fix listedDEBIAN-CVE-2026-83610
Debian14node-xmldom0.9.12-1DEBIAN-CVE-2026-83610
Ubuntu20.04:LTS, 22.04:LTS, 24.04:LTS and 2 morenode-xmldomno fix listedUBUNTU-CVE-2026-83610
Azure Linux3python-tensorboardno fix listedAZL-99339

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This Moderate flaw in xmldom allows for XML fragment injection. Exploitation requires an application to explicitly create and serialize an EntityReference with an invalid name, which is not a default or common operation in Red Hat products, thus limiting the attack surface.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Build of Podman Desktoprh-podman-desktop.gitFix deferred
Red Hat Developer Hub 1rhdh/rhdh-hub-rhel9Fix deferred
Red Hat Enterprise Linux 10grafanaFix deferred
Red Hat Enterprise Linux 8grafanaFix deferred
Red Hat Enterprise Linux 9grafanaFix deferred
Red Hat Fuse 7xmldomOut of support scope
Red Hat OpenShift AI (RHOAI)rhoai/odh-mlflow-rhel9Fix deferred
Red Hat OpenShift Container Platform 4openshift4/ose-consoleFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-83610.

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-104 Cross Zone Scripting Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON