cve.bz

CVE-2026-83617 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.9.12.

On this page
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.11 until 0.9.12, the requireWellFormed: true element and attribute name checks use the anchored QName_exact expression produced by reg() in lib/grammar.js, which inherits the multiline flag. A name with a valid first line followed by U+000A, U+000D, U+2028, or U+2029 and breakout markup therefore passes validation and is emitted verbatim in element start and end tags or attribute names. This bypasses the strict-serialization checks introduced for the earlier element-name and attribute-name injection advisories, while the default serialization path remains outside the strict guarantee. This issue is fixed in @xmldom/xmldom version 0.9.12.

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; 48th 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.
CWEs
CWE-91 XML Injection (Blind XPath Injection)
CWE-625 Permissive Regular Expression
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-83617 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-83617?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-83617?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-83617 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.9.11, < 0.9.12
@xmldom xmldom>= 0.9.11, < 0.9.12

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jxjr-3g7g-3944npm@xmldom/xmldom>=0.9.11 <0.9.120.9.12

Linux distributions

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

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. 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

Red Hat has evaluated this vulnerability as having an Important severity rating because remote actors can inject arbitrary XML markup into serialized outputs without requiring prior authentication, potentially compromising data integrity across dependent services. To exploit this issue, an affected application must dynamically create DOM element or attribute identifiers directly from unvalidated external input and subsequently serialize the tree using strict well-formedness validation. In standard deployments, user-supplied content is generally restricted to text nodes or attribute values rather than structural tag names, substantially reducing real-world exposure.

ProductPackageStateAdvisory
Red Hat Build of Podman Desktoprh-podman-desktop.gitNot affected
Red Hat Developer Hub 1rhdh/rhdh-hub-rhel9Not affected
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 OpenShift AI (RHOAI)rhoai/odh-mlflow-rhel9Not 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-83617.

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