CVE-2026-114938 RCE in OpenJDK: Everything You Need to Know

Detect and mitigate Java4Shell (CVE-2026-114938), a critical 9.2 RCE vulnerability affecting OpenJDK and major Java-based applications.

On November 17, 2026, details emerged exposing a critical remote code execution (RCE) vulnerability in OpenJDK, tracked as CVE-2026-114938 (dubbed "Java4Shell") with a CVSSv4.0 score of 9.2. The bug exists in the optimized assembly code handling AVX-512 Base64 decoding, allowing remote unauthenticated attackers to cause heap memory corruption. Triggering this flaw on affected systems can lead to remote code execution. 

The "Java4Shell" vulnerability and exploit were discovered and disclosed by security firm Calif.

What is CVE-2026-114938?

CVE-2026-114938 is a memory-corruption vulnerability residing in the optimized Base64 decoding intrinsic engine of the Java Virtual Machine (JVM). To maximize performance, OpenJDK uses an optimized implementation on supported x86-64 processors, based on AVX-512 VBMI instructions. However, the optimized assembly code miscalculates the output array bounds when handling inputs that contain an unexpected number of trailing padding characters (=).

When an input containing a specific sequence -such as 64 A characters followed by a single = - is parsed, the decoder's length calculation underflows to a negative value. This calculation mismatch causes an out-of-bounds write past the allocated heap memory buffer. Attackers can leverage this to overwrite adjacent object metadata, which can lead to code execution. We have proved that remote exploitation is feasible against standard Java applications such Jenkins, Confluence, and Apache Tomcat.

Wiz Research data: what’s the risk to cloud environments?      

Like other memory safety issues, exploitation is possible with AI, but is not trivial. Our AI based vulnerability research harness, Wiz Atlas, managed to find and build a proof-of-concept exploit for this vulnerability within 2 hours, even before the full details were disclosed. Having said that, generalizing the exploit for an arbitrary target is difficult. We should expect adversaries to target commonplace Java applications, where specific builds and memory layouts repeat across targets. Motivated adversaries may tailor exploits with AI for specific targets, including home-grown applications.

Web Application Firewalls can help mitigate some of the exploits as they emerge in the wild. Since this vulnerability is rooted in OpenJDK itself, many possible code paths using user inputs may lead into the vulnerable code path, so it’s unlikely that WAF rules will be able to cover all possible paths, and will never be able to cover home grown applications completely. The best solution is upgrading to the latest OpenJDK version.

Prioritize externally facing, packaged Java applications, and make sure they are either patched or restricted from public access. Upgrade home-grown Java applications and update to the latest OpenJDK version containing the fix.

Which products are affected?

The vulnerability affects OpenJDK versions 17.0.6 and later, as well as downstream distributions, provided they run on x86-64 hardware supporting AVX-512 VBMI instruction sets (ARM64 processors are unaffected). Affected software distributions and hardware include:

  • OpenJDK Distributions: Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, and Oracle Java SE (specifically versions 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3).

  • Vulnerable CPU Architectures: Intel Xeon (Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids) and AMD EPYC/Ryzen (Zen 4 or newer).

  • Proven Vulnerable Applications (Pre-Auth RCE): Atlassian Jira, Atlassian Confluence, Keycloak, JFrog Artifactory, Jenkins, and custom frameworks built on Spring Boot, Apache Struts, Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, Netflix Spinnaker and Apache Tomcat.

Which actions should security teams take?

Security teams should immediately prioritize the following mitigation steps:

  1. Audit and Patch: Identify all systems running OpenJDK 17.0.6 or later on AVX-512-capable x86-64 hardware. Apply the official security patches released on November 17, 2026, or update to downstream vendor-supplied builds immediately.

  2. Verify Hardware Vulnerability: Run the following command on Linux systems to check if your infrastructure is physically affected:

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

If all four CPU flags are present in the output, the host runs the vulnerable hardware execution path.

  1. Implement JVM Runtime Workarounds: If immediate patching is not possible, apply one of the following flags to JVM startup parameters to completely neutralize the vulnerability. They may have performance impact on the application.

    1. Disable Base64 Intrinsics (Recommended): -XX:-UseBASE64Intrinsics

    2. Disable AVX-512 execution (x86-64 only): -XX:UseAVX=2

  2. Isolate Internet-Facing Services: Temporarily restrict external network access to vulnerable management portals (e.g., Jira, Jenkins, Keycloak) until mitigations or updates are deployed.

Wiz customers can use the pre-built query and advisory in the Wiz Threat Center to search for vulnerable instances in their environment.

References

Continue reading

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management