Quick answers
- Is CVE-2026-110938 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110938 being exploited in the wild.
- How severe is CVE-2026-110938?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- Eclipse Openj9 up to 0.63.0.
- Is there a fix for CVE-2026-110938?
- Yes: fixed in OpenJ9 0.63.0 and later (patched in main branch via PR #25011, merged October 20, 2026). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110938 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110938?
- 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: OpenJ9 0.63.0 and later (patched in main branch via PR #25011, merged October 20, 2026)
Technical details
The JITServer protocol parses serialized messages with data descriptors for parameters; a malicious actor can craft descriptors with misrepresented size, padding, and offset values that cause out-of-bounds reads when computing payload sizes. The vulnerability affects message and reply handling in both directions (CWE-125 out-of-bounds read, CWE-20 improper input validation). The fix adds descriptor validation to ensure payload calculations cannot exceed allocated buffer bounds.
Affected products
- Eclipse OpenJ9 up to 0.63.0
Timeline
- 2026-10-21: disclosed
- 2026-10-20: patched