Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97400 Overview
CVE-2026-97400 affects Eclipse OpenJ9 versions up to 0.63. The vulnerability resides in the Diagnostic Tool Framework for Java (DTFJ) and the jdmpview tool used to analyze diagnostic dump bundles. When an analyst opens a maliciously crafted dump bundle, the tool processes XML content without properly restricting external entity resolution. This XML External Entity (XXE) weakness [CWE-611] allows the bundle to reference arbitrary local files on the analyst's machine and exfiltrate their contents to an attacker-controlled remote host.
Critical Impact
Opening an untrusted diagnostic dump bundle can leak arbitrary local files from the analyst's workstation to a remote attacker.
Affected Products
- Eclipse OpenJ9 versions up to and including 0.63
- jdmpview diagnostic analysis tool shipped with OpenJ9
- Applications and tooling built on the DTFJ API
Discovery Timeline
- 2026-10-20 - CVE CVE-2026-97400 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-97400
Vulnerability Analysis
The flaw is an XML External Entity injection in the DTFJ bundle-parsing path used by jdmpview. Diagnostic dump bundles contain XML metadata describing dump contents and layout. The underlying XML parser resolves external entities and system identifiers declared in the Document Type Definition (DTD) without hardening. An attacker-controlled bundle can therefore declare an entity that references a local file path and resolves through an external URL, causing the parser to read the file and transmit it to a remote host during parse.
This class of weakness is tracked under [CWE-611: Improper Restriction of XML External Entity Reference]. Exploitation requires an analyst to open the attacker-supplied bundle, which is a realistic scenario when triage teams receive dumps from external parties, customers, or third-party support channels.
Root Cause
The root cause is an XML parser configuration in the DTFJ code path that fails to disable external general entities, external parameter entities, and DTD processing. Secure defaults such as FEATURE_SECURE_PROCESSING and disallow-doctype-decl are not enforced before parsing untrusted bundle content.
Attack Vector
An attacker crafts a diagnostic dump bundle whose embedded XML declares an external entity referencing a sensitive local file, for example /etc/passwd or an application configuration file. The entity is referenced within an element the parser evaluates. When the analyst runs jdmpview or an equivalent DTFJ consumer against the bundle, the parser reads the file and transmits its contents to the attacker's remote endpoint through the entity resolution request. User interaction is required, and the attack executes with the privileges of the analyst running the tool.
No verified public proof-of-concept code is available. Technical details are documented in the Eclipse OpenJ9 Pull Request #25003 and the Eclipse Vulnerability Report.
Detection Methods for CVE-2026-97400
Indicators of Compromise
- Outbound network connections from jdmpview, java, or DTFJ-based analysis processes to untrusted external hosts during bundle analysis.
- Diagnostic dump bundles containing XML files with <!DOCTYPE> declarations, <!ENTITY ... SYSTEM ...> definitions, or external parameter entity references.
- Access by the Java process to sensitive files outside the bundle extraction directory shortly after a bundle is opened.
Detection Strategies
- Inspect dump bundles with static scanning that flags DTD declarations and external entity references before analysts open them.
- Monitor process-to-network telemetry on analyst workstations for connections initiated by java processes running DTFJ.
- Alert on file reads by the jdmpview process targeting paths outside the designated working directory.
Monitoring Recommendations
- Baseline normal jdmpview behavior and alert on any outbound HTTP, FTP, or DNS traffic from the parsing process.
- Enable EDR file access auditing on analyst machines to capture reads of credential stores, SSH keys, and configuration files during dump analysis.
- Centralize logs from analyst workstations and correlate dump-bundle open events with network egress to third-party domains.
How to Mitigate CVE-2026-97400
Immediate Actions Required
- Upgrade Eclipse OpenJ9 and the DTFJ tooling to a fixed release above version 0.63 as soon as a patched build is available.
- Treat all third-party diagnostic dump bundles as untrusted and analyze them only inside isolated, network-restricted virtual machines.
- Verify the integrity and origin of any dump bundle before opening it with jdmpview or DTFJ consumers.
Patch Information
The fix is tracked in the upstream project through Eclipse OpenJ9 Pull Request #25003, with coordination documented in the Eclipse CVE Assignment. The patch hardens the XML parser configuration used by DTFJ so that external entity resolution and DTD processing are disabled when reading bundle metadata. Apply the fixed OpenJ9 build on every workstation that runs diagnostic analysis.
Workarounds
- Run jdmpview on an air-gapped or egress-filtered host so external entity resolution cannot reach attacker infrastructure.
- Pre-process incoming bundles to strip or validate XML files, rejecting any that contain <!DOCTYPE> or <!ENTITY> declarations.
- Restrict the analyst account's file system access to only the bundle working directory while analysis is in progress.
# Block outbound traffic from the DTFJ analysis host at the firewall
# Example: default-deny egress with only internal update sources allowed
iptables -P OUTPUT DROP
iptables -A OUTPUT -o lo -j ACCEPT
iptables -A OUTPUT -d 10.0.0.0/8 -j ACCEPT
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

