Published November 18, 2026. We will update this post as new information becomes available. 

On November 17, 2026, security firm Calif publicly disclosed Java4Shell (CVE-2026-114938), a critical memory-corruption vulnerability in the Base64 decoder of OpenJDK, the most widely used Java runtime. The OpenJDK Vulnerability Group published a fix the same day. Because Java runs a large share of enterprise applications, and because the flaw sits in the runtime rather than in a library, many organizations will need to act. 

Imperva is providing protection to Cloud WAF, Imperva for AWS and Imperva for Google Cloud customers today. Manual mitigation instructions for Imperva WAF Gateway customers are available. In addition, a new Imperva WAF Gateway version with dedicated protection is about to be released in the next following days. Details are below, but first, the vulnerability itself. 

What is Java4Shell? 

Base64 is a common way of representing binary data as text. Applications use it in authentication headers, tokens, file uploads and API messages, so Java services often decode Base64 that came straight from the network. 

To decode Base64 faster, OpenJDK uses specialized CPU instructions on supported processors. The hand-written machine code that handles the final characters of the input miscalculates how much data to write when the input ends in padding. As a result, the decoder writes beyond the end of its output buffer on the Java heap. Java then rejects the malformed input, but neighboring objects may already be corrupted. 

With careful exploitation, an unauthenticated remote attacker could leak memory contents or achieve remote code execution. Working exploits have been demonstrated against several widely used Java applications in their default configurations, including identity, CI/CD, collaboration and artifact-management platforms, as well as sample applications built on popular frameworks. A Java client that connects to a malicious TLS server can also be compromised, so the issue is not limited to servers that accept inbound requests. 

There is no universal exploit. Each target application requires its own tailored approach, and an unsuccessful attempt can crash the Java process. That should not be read as reassurance: the researchers report that they found the bug in about an hour and built the first working exploit in a few more. 

Severity 

The vulnerability is rated 9.2 (Critical) under CVSS 4.0. The OpenJDK advisory lists a CVSS 3.1 score of 8.1. The two scores use different scales and are not directly comparable. 

Who is affected? 

According to the OpenJDK advisory dated November 17, 2026, CVE-2026-114938 affects Java 17, 21, 25 and 27. For Java 17, the affected range begins at 17.0.6. Java 8 and 11 are not listed in the advisory, although Oracle lists its Java 8 performance build (8u511b33-perf) as vulnerable. 

Because the issue is in OpenJDK code, distributions built from it are also affected, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle OpenJDK, Oracle Java SE and Oracle GraalVM for JDK. 

The vulnerable code is hardware-specific. It requires an x86-64 processor with AVX-512 VBMI support, which includes Intel Xeon (Ice Lake and newer) and AMD EPYC and Ryzen (Zen 4 and newer). ARM64 processors are not affected. 

Many applications bundle their own Java runtime, so checking the system-wide Java installation is not enough. 

What you should do 

  • Patch. Update your Java runtime to the fixed build from your Java vendor, and then restart every Java process. This is the only complete remediation. Replacing files on disk does not change a JVM that is already running. Rebuild container images on a patched base image, and ask vendors of third-party products with bundled runtimes for updates. 
  • Inventory. Identify every Java runtime in your environment, including containers and bundled runtimes, and check which of them run on x86-64 hosts with AVX-512 VBMI. Because the flaw is in the JDK, dependency scanners that look for vulnerable libraries will not find it. 
  • Use a temporary JVM option if you cannot patch immediately. Start OpenJDK with -XX:-UseBASE64Intrinsics, which disables hardware-accelerated Base64 handling, or with -XX:UseAVX=2, which disables AVX-512. Use the second option on x86-64 hosts only, since OpenJDK on ARM does not recognize it and will fail to start. Both require a restart, may affect performance for Base64-heavy workloads, and should be tested first. Neither replaces patching. 
  • Be careful with proof-of-concept code. Repositories using the CVE identifier are already appearing, and fake exploits are a common way to spread malware after high-profile disclosures. Review any code before running it, and never run it on production systems. 

How Imperva protects you 

Starting today, November 18, Imperva Cloud WAF, Imperva for AWS and Imperva for Google Cloud customers are protected against attempts to exploit CVE-2026-114938 in common base64 input fields. If you have a custom Java application running a vulnerable version exposed to the internet, you are advised to contact our support team for further guidance.  

Manual mitigation instructions for Imperva WAF Gateway customers are available. In addition, a new Imperva WAF Gateway version with dedicated protection is about to be released in the next following days. We will publish the version number and upgrade instructions in the release notes and update this post when it is released. 

A web application firewall is a valuable layer of defense, especially while patching is under way, but it does not replace patching. Exploitation depends on how each application uses Base64, and the fix for this vulnerability is in the Java runtime itself. We strongly recommend that you apply your Java vendor’s update as well. 

What’s next 

We continue to monitor the situation, including the publication of further technical details and any reports of exploitation, and will update this post and our protections as needed. If you have questions, please contact our support team. 

The post Java4Shell (CVE-2026-114938): What You Need to Know and How Imperva Protects You appeared first on Blog.