Quick answers
- Is CVE-2026-111075 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-111075 being exploited in the wild.
- How severe is CVE-2026-111075?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- Eclipse Openj9 0.8.0 to 0.62.x.
- Is there a fix for CVE-2026-111075?
- Yes: fixed in 0.63.0. Until then: Restrict network access to JITServer endpoints to trusted compilation clients only; disable JITServer if remote compilation optimization is not required and local JIT compilation is sufficient. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-111075 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-111075?
- Check whether you run Eclipse Openj9 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.63.0
Restrict network access to JITServer endpoints to trusted compilation clients only; disable JITServer if remote compilation optimization is not required and local JIT compilation is sufficient.
Technical details
The vulnerability is an unsigned integer underflow (CWE-191) in DataDescriptor::getPayloadSize() resulting from insufficient cross-field validation of the _size, _paddingSize, and _dataOffset fields during message deserialization. An unauthenticated remote attacker can craft a network payload where _size is less than the sum of _paddingSize and _dataOffset, causing getPayloadSize() to return an extremely large value that leads to out-of-bounds heap reads (CWE-125) and immediate process termination (SIGSEGV).
Affected products
- Eclipse OpenJ9 0.8.0 to 0.62.x
Timeline
- 2026-10-21: disclosed
- 2026-10-20: patched