Patch Eclipse OpenJ9 to Stop Remote JITServer Denial of Service Attacks
Unauthenticated attackers can crash JVM processes in OpenJ9 versions before 0.63.0 by sending malformed payloads to the JITServer component.

Key points
- CVE-2026-110938 allows remote denial of service via out-of-bounds heap reads.
- The flaw affects Eclipse OpenJ9 versions prior to 0.63.0.
- No authentication is required to exploit the JITServer component.
Eclipse OpenJ9 versions prior to 0.63.0 contain a high-severity vulnerability that allows unauthenticated remote attackers to crash Java Virtual Machine processes. The flaw resides in the JITServer component, which handles protocol messages and replies without proper boundary checks. According to the National Vulnerability Database, this issue is tracked as CVE-2026-110938 and carries a CVSS score of 8.7.
The risk
The vulnerability stems from improper input validation during network message handling. An attacker can transmit malformed payloads that trigger out-of-bounds heap reads within the JITServer daemon. This action causes an immediate segmentation fault, resulting in a denial of service for the affected JVM process. The Common Weakness Enumeration identifies the underlying issues as CWE-125 and CWE-20.
Who is exposed
Any organization running Eclipse OpenJ9 versions before 0.63.0 is exposed to this risk. The JITServer component is often used in distributed computing environments where JVMs offload just-in-time compilation tasks. Because the attack requires no authentication, any system with network access to the JITServer daemon is potentially vulnerable to remote exploitation.
Cost and compliance
The source material does not provide specific details regarding financial costs, regulatory compliance impacts, or known incidents of exploitation. The National Vulnerability Database record focuses solely on the technical severity and the nature of the denial of service vulnerability within the specified software versions.
Our take on the response
Security teams should immediately inventory their Java runtime environments to identify any instances of Eclipse OpenJ9. Prioritize patching or upgrading to version 0.63.0 or later to eliminate this high-severity denial of service vector. If immediate patching is not possible, network segmentation should be used to restrict access to the JITServer daemon.
What defenders should look for
Teams usually detect this type of activity by monitoring for unexpected JVM crashes or segmentation faults. Check system logs for sudden termination of Java processes without prior error warnings. Look for network traffic patterns showing malformed packets sent to the JITServer port. Investigate any correlation between external network activity and service unavailability. Implement strict network access controls to limit who can communicate with compilation services. Monitor for repeated connection attempts that result in immediate process termination.
Background: Input validation
Implement strict allowlists for all external data, enforce type and length constraints, and decode inputs before validation. Reject anything that does not match the exact expected format. This prevents injection attacks and buffer overflows by ensuring only safe, predictable data enters your processing logic.
Read the full guide: Input Validation Best Practices to Stop Exploits at the Edge
What to do and how to stay safe: Eclipse OpenJ9
- Inventory all servers and containers to identify running versions of Eclipse OpenJ9.
- Upgrade affected systems to Eclipse OpenJ9 version 0.63.0 or newer once available.
- Restrict network access to the JITServer component to trusted internal hosts only.
- Monitor system logs for unexplained JVM crashes or segmentation fault errors.
Step-by-step guide: Unpatched Software Response: Containment, Recovery, and Prevention Steps
General security guidance from the BlueTeam Herald newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is the CVSS score for CVE-2026-110938?
The CVSS score for this vulnerability is 8.7, which is rated as high severity.
Which versions of Eclipse OpenJ9 are affected?
All versions of Eclipse OpenJ9 prior to 0.63.0 are affected by this vulnerability.
Does the attacker need credentials to exploit this flaw?
No, the National Vulnerability Database states that an unauthenticated remote attacker can exploit this issue.



