Java4Shell is the nickname for CVE-2026-114938, a memory-corruption bug in the Base64 decoder that OpenJDK uses on x86-64 machines with AVX-512 VBMI. The security group Calif says a…
Java4Shell is the nickname for CVE-2026-114938, a memory-corruption bug in the Base64 decoder that OpenJDK uses on x86-64 machines with AVX-512 VBMI. The security group Calif says a 65-character string, 64 letter A's followed by an equals sign, makes the decoder write 62 bytes past the end of a 50-byte array. OpenJDK and Oracle published fixes on November 17. If you run Java 17 or newer, the question is whether any of your servers can reach the broken code path, and that takes about four checks.
TL;DR Calif reports that OpenJDK's AVX-512 Base64 decoder writes 64 bytes into a 50-byte array for a 65-character padded input, so 62 bytes land past the end. Java rejects the input afterwards, which is too late. Scope: OpenJDK 17.0.6 and newer on x86-64 CPUs with AVX-512 VBMI (Intel Ice Lake or later, AMD Zen 4 or later). ARM64 is not affected. Standard Java 8 and 11 are not on this CVE. OpenJDK and Oracle list it at CVSS 3.1 8.1; Calif scores it 9.2 on CVSS 4.0.
Fixed builds exist from Oracle and Amazon Corretto, and Temurin is releasing as testing finishes. Calif says it reached code execution in eleven products. Those are Calif's own tests, the recipes are withheld, and Calif says there is no universal exploit. The mitigation that works everywhere is -XX:-UseBASE64Intrinsics. When I checked on November 18, the CVE was not on CISA's Known Exploited Vulnerabilities list. What is Java4Shell (CVE-2026-114938)? Base64 packs three bytes into four text characters.
It shows up in login headers, file uploads and network messages, so almost every Java server decodes it somewhere. To decode it faster, HotSpot, the JVM inside OpenJDK, can swap in a hand-written assembly routine once a decode call site has been compiled by C2, the optimizing JIT compiler. The routine uses AVX-512 VBMI instructions to process 64 bytes at a time. Calif, a security research group, found the bug in that routine.
Its write-up credits Quang Luong, who says he told the Codex coding agent to audit the JIT compiler, intrinsics, widely used APIs and cryptography. Most of what came back was junk, he says, and then it flagged the Base64 decoder. Calif says it took one hour to find the bug and two more hours to build the first working exploit, for under $200 in tokens. I have not verified any of that; it is Calif's account.
This is a source-linked briefing. Read the original report from Dev Community .