Cyber & AI intelligence
Briefs indexed3793
Issues37
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-114938 2026-11-17

CVE-2026-114938: Java4Shell Heap Overflow in OpenJDK's Base64 Decoder

"A malformed Base64 string can make OpenJDK's hardware-accelerated decoder write past the end of its output array on x86-64 CPUs with AVX-512 VBMI, and the discoverer claims remote code execution in several popular Java…"

A malformed Base64 string can make OpenJDK's hardware-accelerated decoder write past the end of its output array on x86-64 CPUs with AVX-512 VBMI, and the discoverer claims remote code execution in several popular Java products.

What Is It

CVE-2026-114938, nicknamed Java4Shell, is a heap memory-corruption bug in the HotSpot compiler component of OpenJDK. NVD describes it as a flaw Oracle says an unauthenticated attacker can reach over the network by sending data to an API that uses the affected code, such as a web service. The bug sits in an AVX-512 intrinsic that speeds up Base64 decoding. Calif, the discoverer, says crafted input overwrites heap memory after the output array. Upwind reproduced a 62-byte out-of-bounds write that crashes the JVM.

Why It Matters

Exploitation status: As of 2026-11-17, no in-the-wild exploitation has been reported, and the CVE is not in CISA's KEV catalog. Calif published a bounded reproducer that demonstrates the overflow. It is holding back its application-specific exploit chains, which it says target Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, among others. Calif says there is no universal exploit. Upwind has confirmed the crash and heap corruption, but treats code execution as claimed, not verified.

What's Vulnerable

Only a JVM running on an x86-64 CPU with AVX-512 VBMI reaches the bad code. ARM is not affected. Intel Ice Lake and newer Xeons, and AMD Zen 4 and newer, qualify. On Linux, check /proc/cpuinfo for avx512f, avx512bw, avx512vbmi and bmi2.

You are exposed if an affected JVM decodes Base64 that an attacker controls, such as HTTP Basic auth headers or JWTs. Upwind confirmed pre-auth paths in Spring Security, Tomcat, Jetty 12 and Auth0's java-jwt.

Oracle, Amazon Corretto, Temurin, Zulu, Red Hat and other builds share the code. The 17.0.6 lower bound comes from Calif and Upwind. Oracle credits Quang Luong of Calif.io with the report.

Patch Status

Oracle fixed the bug in its November 17, 2026 Critical Security Patch Update, and the OpenJDK advisory published the same day lists it as fixed. OpenJDK marks the 17, 21, 25 and 27 lines as affected, up to and including 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3. Upwind reports the fixed Oracle builds as 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Amazon Corretto's changelogs list the CVE as fixed in 17.0.21.1.2, 21.0.13.1.2 and 25.0.5.1.2. We could not confirm fixed builds for Temurin, Zulu, Microsoft, Red Hat, Debian or Ubuntu as of this writing.

Calif and Upwind both document -XX:-UseBASE64Intrinsics as a workaround that stopped the overflow in testing. Upwind and Calif report that -XX:UseAVX=2 also prevented the overflow in testing; it works on x86-64 only and stops ARM JVMs from starting. Neither Oracle nor OpenJDK has endorsed these flags.

Required action: Inventory your Java runtimes and upgrade to the fixed builds above, or your distribution's equivalent once published. Start with internet-facing services on AVX-512 hardware. Until you can patch, apply -XX:-UseBASE64Intrinsics after testing it, and restrict external access to affected services.

Sources