High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Mitigation available
Distribution package intelligence
Ubuntu vendor package status
Canonical’s release and source-package findings are shown separately from local repository availability.
1 package state
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
Ubuntu release
Source package
Vendor state
Fixed version
Evidence
Ubuntu 24.04 LTSnoble · standard archive
node-xmldom
Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
1 current
CVE-2026-83608 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityxmldom: @xmldom/xmldom: xmldom: XML Markup Injection via DocType Name Bypass
11 known affected
The vendor explicitly identifies these products as affected by this CVE.
rh-podman-desktop.git as a component of Red Hat Build of Podman Desktop
rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub
grafana as a component of Red Hat Enterprise Linux 10
grafana-selinux as a component of Red Hat Enterprise Linux 10
grafana.src as a component of Red Hat Enterprise Linux 10
grafana as a component of Red Hat Enterprise Linux 9
grafana-selinux as a component of Red Hat Enterprise Linux 9
grafana.src as a component of Red Hat Enterprise Linux 9
xmldom as a component of Red Hat Fuse 7
rhoai/odh-mlflow-rhel9 as a component of Red Hat OpenShift AI (RHOAI)
openshift4/ose-console as a component of Red Hat OpenShift Container Platform 4
Summary
A flaw was found in xmldom, a JavaScript module for parsing and serializing XML. A remote attacker can exploit this vulnerability by providing a specially crafted `DocumentType.name` containing characters like `>` or whitespace. This bypasses the `requireWellFormed` validation, allowing the injection of arbitrary XML markup. Such injection can lead to unintended modifications of the XML document structure, potentially resulting in arbitrary code execution or information disclosure within applications that process the affected XML.
Remediation
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.
Optional official sources
National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.
Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.
Official European source
ENISA European Vulnerability Database
Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
8.7 · CVSS 4.0
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.
Mitigation available
01
What, why and how
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, the DOCUMENT_TYPE_NODE branch in lib/dom.js validates publicId, systemId, and internalSubset under requireWellFormed: true but emits DocumentType.name verbatim. A name containing > or whitespace can terminate the <!DOCTYPE ...> declaration and inject sibling markup; the value can be supplied through createDocumentType() on the 0.8.x and unscoped lines or through a direct DocumentType.name property write on every affected line. The default path and legacy creation-time behavior remain permissive, while the vulnerable strict path fails to enforce an XML Name. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
What
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, the DOCUMENT_TYPE_NODE branch in lib/dom.js validates publicId, systemId, and internalSubset under requireWellFormed: true but emits DocumentType.name verbatim. A name containing > or whitespace can terminate the <!DOCTYPE ...> declaration and inject sibling markup; the value can be supplied through createDocumentType() on the 0.8.x and unscoped lines or through a direct DocumentType.name property write on every affected line. The default path and legacy creation-time behavior remain permissive, while the vulnerable strict path fails to enforce an XML Name. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
Why
The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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, the DOCUMENT_TYPE_NODE branch in lib/dom.js validates publicId, systemId, and internalSubset under requireWellFormed: true but emits DocumentType.name verbatim. A name containing > or whitespace can terminate the <!DOCTYPE ...> declaration and inject sibling markup; the value can be supplied through createDocumentType() on the 0.8.x and unscoped lines or through a direct DocumentType.name property write on every affected line. The default path and legacy creation-time behavior remain permissive, while the vulnerable strict path fails to enforce an XML Name. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.
Why
The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No confirmed evidence
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material ?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.Reference recorded
CISA Vulnrichment records proof-of-concept exploitation in its SSVC data. BlackTree has not independently executed or validated exploit material.
Likely attack path
a network path → XML Injection (aka Blind XPath Injection) → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness ?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-91: XML Injection (aka Blind XPath Injection). The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system.
CVSS vector ?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
Operational remediation based on structured source evidence.
Status ?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
Workaround
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.
04
Evidence and provenance
Published 1 Sept 2026 · Last source change 4 Sept 2026, 01:56 UTC · CWE-91 · XML Injection (aka Blind XPath Injection)
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source ?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.FIRST · tracked since 2026-09-02
European sourceENISA EUVD · EUVD-2026-69219
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled
Core structured fields are present and their contributing authorities are shown above.
Affected versionsThe structured affected or fixed version information changed.
Before
rh-podman-desktop.git as a component of Red Hat Build of Podman Desktop; rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub; grafana as a component of Red Hat Enterprise Linux 10; grafana-selinux as a component of Red Hat Enterprise Linux 10; grafana.src as a component of Red Hat Enterprise Linux 10; grafana as a component of Red Hat Enterprise Linux 8; grafana-azure-monitor as a component of Red Hat Enterprise Linux 8; grafana-cloudwatch as a component of Red Hat Enterprise Linux 8; grafana-elasticsearch as a component of Red Hat Enterprise Linux 8; grafana-graphite as a component of Red Hat Enterprise Linux 8; grafana-influxdb as a component of Red Hat Enterprise Linux 8; grafana-loki as a component of Red Hat Enterprise Linux 8; grafana-mssql as a component of Red Hat Enterprise Linux 8; grafana-mysql as a component of Red Hat Enterprise Linux 8; grafana-opentsdb as a component of Red Hat Enterprise Linux 8; grafana-postgres as a component of Red Hat Enterprise Linux 8; grafana-prometheus as a component of Red Hat Enterprise Linux 8; grafana-selinux as a component of Red Hat Enterprise Linux 8; grafana-stackdriver as a component of Red Hat Enterprise Linux 8; grafana.src as a component of Red Hat Enterprise Linux 8; grafana as a component of Red Hat Enterprise Linux 9; grafana-selinux as a component of Red Hat Enterprise Linux 9; grafana.src as a component of Red Hat Enterprise Linux 9; xmldom as a component of Red Hat Fuse 7; rhoai/odh-mlflow-rhel9 as a component of Red Hat OpenShift AI (RHOAI); openshift4/ose-console as a component of Red Hat OpenShift Container Platform 4
After
rh-podman-desktop.git as a component of Red Hat Build of Podman Desktop; rhdh/rhdh-hub-rhel9 as a component of Red Hat Developer Hub; grafana as a component of Red Hat Enterprise Linux 10; grafana-selinux as a component of Red Hat Enterprise Linux 10; grafana.src as a component of Red Hat Enterprise Linux 10; grafana as a component of Red Hat Enterprise Linux 9; grafana-selinux as a component of Red Hat Enterprise Linux 9; grafana.src as a component of Red Hat Enterprise Linux 9; xmldom as a component of Red Hat Fuse 7; rhoai/odh-mlflow-rhel9 as a component of Red Hat OpenShift AI (RHOAI); openshift4/ose-console as a component of Red Hat OpenShift Container Platform 4
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
