What happened with Java4Shell?
On November 17, 2026, the OpenJDK Vulnerability Group and Oracle disclosed CVE-2026-114938, a flaw in the HotSpot hotspot/compiler component rated CVSS 3.1 8.1. Oracle lists it as remotely exploitable without authentication or user interaction, with high attack complexity. Oracle credits Quang Luong of Calif.io, which named the bug Java4Shell.
In its writeup, Calif explains that the x86-64 AVX-512 code HotSpot uses to speed up java.util.Base64 decoding miscalculates the output length when malformed input ends in = padding. A 64-byte masked write then runs about 62 bytes past the end of the output array. The trigger is short: a run of A characters and a stray =. Calif published a proof of concept that triggers the overflow and is holding back its exploit chains. VulnCheck says the bug isn't known to be exploited in the wild, that crashing a JVM is easy, and that code execution needs heap grooming plus a memory leak.
Which Java versions and systems are affected?
- HotSpot-based OpenJDK 17.0.6 and later, and the 21, 25 and 27 lines. That includes builds such as Eclipse Temurin, Amazon Corretto, Azul Zulu, Red Hat, Microsoft, BellSoft Liberica, SAP SapMachine, Oracle Java SE and Oracle GraalVM for JDK, per Calif.
- Only on x86-64 CPUs with AVX-512 VBMI, such as Intel Xeon Ice Lake and later and AMD Zen 4 and later. On Linux,
/proc/cpuinfoshowsavx512f,avx512bw,avx512vbmiandbmi2. - ARM64 hosts are not affected. OpenJDK's risk matrix doesn't list Java 8 or 11 for this CVE.
- The service has to decode untrusted Base64 with
java.util.Base64, for example in authentication, file uploads or network messages.
How to check if you're affected
- Run
java -versionon each host or inside each running container to confirm the JVM build and version line. - Check the CPU the JVM actually runs on:
grep -o -w -Efor the four flags above in/proc/cpuinfo. A container image doesn't decide the CPU. The node it's scheduled on does, and mixed node pools can put one service on both. - Check whether the Base64 intrinsic is on with
java -XX:+UnlockDiagnosticVMOptions -XX:+PrintFlagsFinal -version, and look forUseBASE64IntrinsicsandUseAVX. - List services that decode Base64 from requests, starting with internet-facing ones and anything that parses tokens, HTTP Basic auth headers or uploads.
- Mark any service whose host CPU or JVM you can't see as unknown, not cleared.
What to do now
- Confirm the fixed build for your Java distribution in that vendor's own advisory, then update and restart every affected JVM. A new JDK on disk doesn't fix a JVM that's already running.
- Until then, consider the workarounds Calif and VulnCheck describe:
-XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsicsto disable the Base64 intrinsic, or-XX:UseAVX=2to disable AVX-512. Calif warns that ARM builds of OpenJDK won't start withUseAVX=2, so set it only on x86-64. - Rebuild images that pin or float on an affected JDK tag, so the next deploy doesn't bring the old runtime back.
- Don't rely on request-size limits. The malformed input that triggers the overflow is short.
Why repository scans can't settle Java4Shell exposure
A repository shows which services use Java and which language level they build against. It doesn't show the JVM build that's deployed, the CPU it lands on, or whether untrusted input reaches the affected decoder. Those live in base images, deploy configuration, the cloud inventory and the running process. Repository, container and cloud evidence together can narrow the list to the services that need a runtime check. They can't replace that check.
Where Nullify fits
How Nullify Covers This Class of Attack
Nullify moves actively exploited vulnerabilities in the dependencies and images you use up the backlog as soon as they're disclosed, and prepares the version change as a pull request for each owner to review.
The vulnerable component is the Java runtime in your images and hosts, so the version lives in base images and deploy config, and the CPU depends on where the service runs.
Frequently Asked Questions
What is Java4Shell?
Java4Shell is the name for CVE-2026-114938, a heap overflow in HotSpot's hardware-accelerated Base64 decoder on x86-64 CPUs with AVX-512 VBMI. OpenJDK and Oracle disclosed it on November 17, 2026, with a CVSS 3.1 score of 8.1.
Is Java4Shell exploited in the wild?
VulnCheck said on November 17, 2026 that it isn't known to be exploited in the wild, and it wasn't in CISA's KEV catalog on November 18. Calif's public proof of concept triggers the overflow, so patch internet-facing services first.
Are ARM servers affected by Java4Shell?
No. The vulnerable code is HotSpot's x86-64 AVX-512 Base64 path, so ARM64 hosts such as AWS Graviton don't run it. The same container image can be exposed on an x86 node with AVX-512 VBMI and not on an ARM node.
How do I mitigate Java4Shell before patching?
Calif and VulnCheck describe disabling the Base64 intrinsic with -XX:-UseBASE64Intrinsics, or disabling AVX-512 with -XX:UseAVX=2 on x86-64 only. Then confirm the fixed build in your Java vendor's advisory, update and restart the JVM.
Update Log
- Nov 18, 2026: page published from the OpenJDK and Oracle advisories (Nov 17), Calif's writeup and VulnCheck's analysis.