Eclipse OpenJ9 CVE-2026-97400

Requires an attacker-supplied diagnostic dump bundle (zip) whose embedded XML metadata contains a malicious external entity, AND an analyst who actively opens that bundle with the jdmpview tool or equivalent legacy DTFJ/DTFJImageFactory code in Eclipse OpenJ9 at or below version 0.63. Limiting factors: exploitation is LOCAL (the victim must receive and open the file - no remote network trigger), depends on social engineering / UI interaction (UI:A), affects only the legacy DTFJ XML parsing path that the fix removes, and the attacker must know or guess the path of a worthwhile local file to exfiltrate and control a reachable remote host to receive it.

This is a moderate, context-dependent risk rather than a mass-exploitation priority. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:A) is self-consistent with the description: the attack is LOCAL and requires active user interaction (UI:A) - an analyst must deliberately open a supplied diagnostic dump bundle with jdmpview or DTFJ code. There is NO remote/network-triggerable path, so despite PR:N (no authentication needed), this cannot be sprayed across the internet. Impact is weighted toward confidentiality (VC:H) because a crafted XXE entity reads an arbitrary local file and exfiltrates it to an attacker host; VI:L/VA:L reflect the limited integrity/availability side effects typical of XXE. No EPSS score, KEV listing, or public POC was provided in the input, so there is no evidence of active exploitation or automatable mass abuse - consistent with SSVC-style 'none/POC-absent' exploitation status. The realistic risk is targeted social engineering against the specific population of engineers/support analysts who triage JVM dump bundles, not broad opportunistic attack. Overall: a legitimate but narrowly-scoped data-exfiltration flaw, not a high-urgency widespread threat.

An attacker crafts a malicious OpenJ9 diagnostic dump bundle whose XML metadata contains an external entity (XXE) referencing a sensitive local file and an attacker-controlled host. The attacker tricks a support engineer or analyst into opening the bundle with jdmpview (or DTFJ-based tooling); the vulnerable XML parser resolves the entity, reads the named local file, and sends its contents to the remote host. No public exploit was identified at time of analysis, though the fixing PR (#25003) reveals the vulnerable legacy DTFJ XML parsing path. Because AV:L and UI:A apply, success depends entirely on the analyst actively opening the attacker-supplied file.