What is Java4Shell CVE-2026-114938?
Java4Shell, otherwise known as CVE-2026-114938, is a reported Remote Code Execution vulnerability in Java, the widely used programming language and runtime that many enterprise applications and servers rely on to run code. The vulnerability is believed to be exploitable by an unauthenticated, external attacker, and can be used to execute code. Oracle and OpenJDK have not yet confirmed the technical details, the affected component, or whether a fix is available, but details are expected on November 17th.
OpenJDK 17.0.6 and later builds are believed to be affected. Oracle’s November 17 Security Patch Update covers 11 separate Java SE vulnerabilities, which are also suspected to address this vulnerability.
| CVE | Description | CVSS | Exploited in the wild |
|---|---|---|---|
| CVE-2026-114938 | Remote Code Execution in Java | Not yet scored | Not reported |
Is Java4Shell being exploited in the wild?
As of November 17, 2026, no exploitation in the wild has been reported.
How is watchTowr helping Java customers?
- watchTowr Instinct assessed CVE-2026-114938 in real time at disclosure as highly likely to be exploited in the wild.
- Adversary Sight engine identified Java instances across client environments and assessed exposure.
- Rapid Reaction identified exposure to this vulnerability across the watchTowr client base, giving teams the time they need to act.
What is Java?
Java is a widely used programming language and runtime that many server-side applications depend on to execute code. In enterprise networks, Java commonly powers web applications, middleware, and other services, some of which are reachable from the internet.
Which Java versions are affected?
| Product | Affected Versions | Fixed Version |
|---|---|---|
| Java 17 (OpenJDK) | 17.0.6 and later | Not yet available |
| Oracle Java SE | 8u511 | Not yet available |
| Oracle Java SE | 8u511-perf | Not yet available |
| Oracle Java SE | 11.0.33 | Not yet available |
| Oracle Java SE | 17.0.21 | Not yet available |
| Oracle Java SE | 21.0.13 | Not yet available |
| Oracle Java SE | 25.0.5 | Not yet available |
| Oracle Java SE | 27.0.1 | Not yet available |
- Exploitation is currently believed to be possible by an unauthenticated, external attacker, with no authentication required.
- No additional information on the prerequisites, configuration, or implementation-specific requirements are known.
Security teams should prioritize identifying internet-facing Java applications and services, and prioritise accelerated patching and remediation where possible.
How do I fix Java4Shell?
Upgrade affected instances of Java to the latest version where possible, or restrict access to internet-facing systems where patching is not possible.
- Inventory every application and server running Java, including bundled runtimes inside application packages and containers.
- Check the exact Java build in use on each host and compare it against vendor updates as they are published.
- Identify which Java services are reachable from the internet, including administrative interfaces.
- Restrict unnecessary external access to Java services with firewalls or access lists until a fix is confirmed.
- Apply the fixed Java build or distributor update as soon as one is published and confirmed to address CVE-2026-114938.
- Restart affected Java processes after installing any update.
What types of threat actors typically exploit this vulnerability?
No attribution has been made public.
