cve.bz

CVE-2026-83607 Blind XPath Injection

8.7 highEPSS 0.6%Fix available

High (8.7). EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in @xmldom/xmldom 0.8.14, 0.9.11.

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.14 and 0.9.11, and in xmldom version 0.6.0 and earlier, Document.createElement(tagName) stores an unvalidated element name and XMLSerializer.serializeToString() emits that name verbatim. The requireWellFormed: true path did not validate the element qualified name or synthesized xmlns:PREFIX declaration, so attacker-controlled tag names could inject attributes, elements, or processing instructions into serialized XML or HTML and could cause cross-site scripting when browser-consumed. The unchecked values violate the XML QName constraint, and default serialization and creation-time createElement() behavior remain permissive. This issue is fixed in @xmldom/xmldom versions 0.8.14 and 0.9.11; no fixed version is available for xmldom.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/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; 50th 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-01. 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-91 XML Injection (Blind XPath Injection)
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-83607 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-83607?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-83607?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-83607 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.14
@xmldom xmldom>= 0.9.0, < 0.9.11

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-w2rr-34g9-rvrjnpm@xmldom/xmldom>=0.9.0 <0.9.110.9.11
GHSA-w2rr-34g9-rvrjnpm@xmldom/xmldom>=0.7.0 <0.8.140.8.14
GHSA-w2rr-34g9-rvrjnpmxmldom<=0.6.0no fix published

Linux distributions

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

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 Important.

Red Hat's statement

A flaw was found in the xmldom JavaScript package. Unvalidated tag names passed to Document.createElement() are emitted verbatim during XMLSerializer.serializeToString() processing. An attacker capable of supplying controlled element names can inject arbitrary attributes, nodes, or processing instructions into serialized XML/HTML output. When rendered within a user's browser context, this input validation failure bypasses QName structural constraints and can result in Cross-Site Scripting (XSS).

Red Hat's mitigation

Sanitize or validate all untrusted element names before passing them to Document.createElement(), ensuring input strictly adheres to valid XML QName specifications prior to serialization.

ProductPackageStateAdvisory
Red Hat Developer Hub 1.9rhdh/rhdh-hub-rhel9:1789554285Fixed 2026-09-21RHSA-2026:69248
Red Hat Build of Podman Desktoprh-podman-desktop.gitAffected
Red Hat Enterprise Linux 10grafanaNot affected
Red Hat Enterprise Linux 8grafanaNot affected
Red Hat Enterprise Linux 9grafanaNot affected
Red Hat Fuse 7xmldomWill not fix
Red Hat Fuse 7xmldom-0.1.27.tgzWill not fix
Red Hat OpenShift AI (RHOAI)rhoai/odh-mlflow-rhel9Not affected
Red Hat OpenShift Container Platform 4openshift4/ose-consoleNot affected

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-83607.

Attack patterns (CAPEC)

  • CAPEC-83 XPath Injection Likelihood: High · Severity: High
  • CAPEC-250 XML Injection Likelihood: High

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

References

Check your stackJSON