cve.bz

CVE-2026-83611

6.9 mediumEPSS 0.6%Fix available

Medium (6.9). 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, DOMParser.parseFromString() can silently accept an end tag such as </a\njunk>, close the element, and discard the trailing content. On 0.9.x, the lib/sax.js end-tag validator inherits the multiline flag from reg(), allowing the first line to satisfy the anchored XML ETag production; older lines have no equivalent residue validation. This parser differential can bypass a parse-before-trust well-formedness gate, although it does not inject the discarded content; onError on 0.9.x and errorHandler on 0.8.x are the relevant reporting interfaces. 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.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/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; 51st 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-1286 Improper Validation of Syntactic Correctness of Input
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-83611 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-83611?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-83611?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-83611 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.9.0, < 0.9.12
@xmldom xmldom>= 0.7.0, < 0.8.15

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6h8r-xr42-gp59npm@xmldom/xmldom>=0.7.0 <0.8.150.8.15
GHSA-6h8r-xr42-gp59npm@xmldom/xmldom>=0.9.0 <0.9.120.9.12
GHSA-6h8r-xr42-gp59npmxmldom<=0.6.0no fix published

Linux distributions

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

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

A flaw was found in the xmldom JavaScript package. The DOMParser.parseFromString() function mishandles malformed XML end tags containing line breaks and trailing content due to incomplete regex boundary validation during parsing. An attacker supplying crafted XML input can cause the parser to prematurely close XML elements and silently discard trailing data, bypassing parse-before-trust well-formedness gates. While this does not result in arbitrary node injection, it causes data integrity issues and potential security logic bypasses in downstream applications relying on strict XML verification.

Red Hat's mitigation

Validate XML inputs against a strict schema or pre-parse XML documents using an alternative conforming parser prior to processing untrusted input with xmldom.

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 7xmldomFix deferred
Red Hat Fuse 7xmldom-0.1.27.tgzFix deferred
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-83611.

Attack patterns (CAPEC)

  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-676 NoSQL Injection Likelihood: High · Severity: High

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

References

Check your stackJSON