Security ·
Java4Shell (CVE-2026-114938): critical OpenJDK flaw can allow remote code execution
Java4Shell is a critical flaw, CVE-2026-114938, in the Base64 decoder of OpenJDK 17 and later on CPUs with AVX-512 VBMI. It scores 9.2 on CVSS 4.0 and Oracle shipped fixes on 17 November 2026.
Security firm Calif disclosed Java4Shell, a critical vulnerability tracked as CVE-2026-114938 in Java. It is a memory corruption bug in the hardware-accelerated Base64 decoder. A malformed input ending in padding makes the decoder compute a negative output length, so it writes a full 64 bytes, 62 bytes past the end of the output array. According to The Hacker News, the flaw can enable pre-authentication remote code execution in applications that decode Base64 from untrusted input, including tools such as Jira, Jenkins and Keycloak.
Datadog Security Labs says the affected range starts at OpenJDK 17.0.6 and covers later versions, but only on x86-64 CPUs with AVX-512 VBMI instructions. Distributions built on OpenJDK are affected too. Qualys notes that the vulnerable code path exists only where the hardware offers those instructions. The score is 9.2 under CVSS 4.0. Calif itself points out that there is no universal exploit, so real risk depends on the specific application.
What should you do? According to Datadog, Oracle released fixed builds on 17 November 2026, for example 17.0.21.1, 21.0.13.1 and 25.0.5.1. Qualys reports that Amazon Corretto also shipped a fix. The Hacker News, however, found that Temurin, Microsoft Build of OpenJDK and Liberica had not listed fixed builds when it checked, and Red Hat had not yet released fixes. Sources disagree on whether Oracle's official notice lists the CVE number, so confirm with the release notes of your own Java vendor.
Until you can patch, Calif recommends starting the JVM with -XX:-UseBASE64Intrinsics, which disables the vulnerable hardware path. It can slow workloads that use Base64 heavily, so test it first. Do you need to act if you do not write Java yourself? Yes, if tools your company or your hosting provider runs are built on it, even when you are not aware of it.
What it means for companies
Start with an inventory: which servers, internal tools and applications in your company run Java 17 or newer, and on what hardware. Then deploy the fixed builds from your vendor, or temporarily switch off the intrinsics. Cyber security covers this work, including checking what really runs on your servers. Ongoing updates are handled by website maintenance and EU hosting, where we decide on patches for you so you do not have to track them yourself.
Sources: The Hacker News: Java4Shell (CVE-2026-114938) enables pre-auth RCE, Datadog Security Labs: Java4Shell, remote code execution in OpenJDK, Qualys: How to find, mitigate and patch Java4Shell