"Java4Shell": Critical OpenJDK Flaw Lets Attackers Run Code Remotely via Malformed Base64 Input
Cisco Talos is tracking a critical vulnerability in OpenJDK Java, CVE-2026-114938, nicknamed "Java4Shell". It has a CVSS 4.0 score of 9.2 and may allow unauthenticated remote code execution (RCE). An attacker can trigger it by sending malformed Base64 input to an affected Java Virtual Machine (JVM).
The flaw affects OpenJDK Java versions 17.0.6 and later running on x86-64 processors with AVX-512 VBMI support enabled. Many commonly deployed Intel and AMD processors include this feature, so the potential attack surface is large and covers both on-premise and cloud environments. The vulnerability has already been tested successfully against a suite of Java applications, and Talos expects more targets to be confirmed over time. Talos credits Calif.io for sharing the details before public disclosure.
Talos has not seen exploitation in the wild yet, but it expects probing attempts to pick up soon after public disclosure. It recommends applying the software update. Where patching cannot happen immediately, the primary interim mitigation is starting the JVM with AVX-512 support disabled, using the option "-XX:UseAVX=2" as described by Talos. This applies only to x86-64 systems, because ARM-based processors will not recognise the option and the application will likely fail to start.
On the detection side, Snort rules, including free community rules, detect malformed Base64 data in specific HTTP request fields tied to the flaw. Talos notes the issue is implementation specific, so coverage targets common vulnerable applications. Splunk customers can use ESCU content that looks for heavily encoded content and for post-exploitation behaviour such as web or application servers spawning shells or running arbitrary commands.
Why it matters
Any internet-facing Java application that accepts Base64 input could be reachable without credentials, so authentication offers no protection here. The hardware condition breaks the assumption that a software flaw is independent of the underlying infrastructure: exposure depends on the CPU features of your servers or cloud instances, which many teams do not track. Because the flaw is implementation specific, network signatures may miss some applications, which makes patching and host-level detection more important.
What to do
- Apply the OpenJDK update for CVE-2026-114938 on affected Java 17.0.6 and later systems.
- Start the JVM with "-XX:UseAVX=2" on x86-64 systems if immediate patching is not possible.
- Avoid using the AVX option on ARM-based systems, as it will likely stop the application from starting.
- Enable Snort community rules and watch for web or application servers spawning shells.