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-111074 Overview
CVE-2026-111074 is a pre-authentication remote denial of service vulnerability in the Eclipse OpenJ9 JITServer component. Versions prior to 0.63.0 are affected. The flaw resides in MessageBuffer::computeRequiredCapacity(), where an integer overflow [CWE-190] triggers an infinite loop in the receiving compilation worker thread. An unauthenticated attacker can open a small number of crafted TCP connections to consume all worker threads at approximately 100% CPU. This silently halts compilation services for every connected client JVM, degrading application performance across the shared JITServer deployment.
Critical Impact
Unauthenticated remote attackers can exhaust the JITServer worker thread pool using a handful of TCP connections, disabling JIT compilation for all connected JVM clients.
Affected Products
- Eclipse OpenJ9 versions prior to 0.63.0
- JITServer component in affected OpenJ9 builds
- JVM deployments relying on affected JITServer instances for remote JIT compilation
Discovery Timeline
- 2026-10-21 - CVE-2026-111074 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-111074
Vulnerability Analysis
The JITServer component accepts TCP connections from client JVMs that offload Just-In-Time compilation work. Each incoming connection begins with a 4-byte length field that the server uses to size an internal message buffer. The MessageBuffer::computeRequiredCapacity() function performs arithmetic on this attacker-controlled length value without adequate bounds validation. A specially crafted length value causes an integer overflow during capacity computation. The resulting undersized or wrapped-around capacity value drives the worker thread into an infinite loop while attempting to satisfy the buffer requirement. Each affected worker consumes approximately 100% of a CPU core and never returns to the pool. Because the JITServer worker pool is finite, a small number of malicious connections exhaust every worker, blocking legitimate client JVMs from obtaining compilation services. The vulnerability requires no authentication, no user interaction, and no prior knowledge of the target environment.
Root Cause
The root cause is an unchecked integer overflow [CWE-190] in MessageBuffer::computeRequiredCapacity(). The function trusts the 4-byte length header from the TCP stream before validating it against reasonable bounds. See the OpenJ9 pull request 25008 for the upstream fix.
Attack Vector
An attacker reaches an exposed JITServer TCP listener over the network and sends crafted length-prefixed messages. Each malicious connection ties up one compilation worker thread indefinitely. Exhausting the pool requires only as many connections as there are workers. The attack produces no crash and emits no application-level error, which delays identification. Refer to the Eclipse vulnerability report #940 for additional technical context.
The exploitation mechanism relies entirely on the overflow in the length field parsing path. No code examples are published alongside the advisory, so defenders should review the referenced patch to understand the specific arithmetic sequence that overflows.
Detection Methods for CVE-2026-111074
Indicators of Compromise
- JITServer worker threads sustaining approximately 100% CPU utilization with no corresponding compilation throughput.
- Multiple inbound TCP connections to the JITServer port that remain established without producing compilation responses.
- Client JVMs reporting stalled or failed remote JIT compilation requests across a shared JITServer instance.
Detection Strategies
- Monitor per-thread CPU time on JITServer processes and alert when worker threads exceed sustained high CPU without processing new requests.
- Compare the number of active TCP sessions on the JITServer port against the configured worker pool size and alert on saturation.
- Correlate JITServer process metrics with client JVM compilation failure logs to surface pool exhaustion events.
Monitoring Recommendations
- Export JITServer metrics (active workers, queued requests, connection counts) to a central telemetry pipeline for alerting.
- Enable network flow logging on the JITServer listening port and alert on unexpected source addresses.
- Track baseline compilation latency from client JVMs and alert on sudden regressions that indicate worker starvation.
How to Mitigate CVE-2026-111074
Immediate Actions Required
- Upgrade Eclipse OpenJ9 to version 0.63.0 or later on all JITServer hosts.
- Restrict network access to the JITServer TCP port using firewalls or security groups so only authorized client JVMs can connect.
- Audit existing JITServer deployments for exposure to untrusted networks and isolate any instance reachable from the public internet.
Patch Information
The fix is tracked in OpenJ9 pull request 25008 and documented in the Eclipse CVE assignment #422. Upgrade to OpenJ9 0.63.0 or newer. Rebuild or redeploy any container images, OpenJDK distributions, or application runtimes that embed OpenJ9 to inherit the fix.
Workarounds
- Disable JITServer where remote JIT compilation is not required and run clients with local JIT only.
- Place JITServer behind a mutually authenticated TLS tunnel or VPN to prevent unauthenticated attackers from reaching the TCP listener.
- Enforce strict allowlists at the network layer that permit only known client JVM source addresses to reach the JITServer port.
# Example iptables rule restricting JITServer access to a trusted client subnet
iptables -A INPUT -p tcp --dport 38400 -s 10.0.0.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 38400 -j DROP
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

