Java4Shell: a flaw in Java’s Base64 decoder allows remote code execution on recent x86 servers

Top-Secured cyber watch: independent analysis based on the sources listed below. Top-Secured is not affiliated with the companies mentioned and will never ask you for your bank details or passwords.

OpenJDK and Oracle fixed CVE-2026-114938 on 17 November, a memory corruption bug in the JVM’s accelerated Base64 decoder on x86-64 processors with AVX-512 VBMI. The researchers who found it say they achieved unauthenticated code execution on Jira, Confluence, Jenkins and Keycloak, and CISA asks for immediate patching.

What happened

On 17 November 2026, the OpenJDK project and Oracle published fixes for CVE-2026-114938, nicknamed Java4Shell by Calif, the company that reported it. The flaw sits in the HotSpot compiler, in the hardware-accelerated routine that decodes Base64. According to Calif, a malformed string of a few dozen characters makes it write past the end of the output buffer, which can leak memory or lead to code execution. The same day, CISA and the Canadian Cyber Centre issued an alert asking organisations to patch immediately. Oracle scores it 8.1 out of 10, Red Hat 9.8 in a preliminary rating.

Who is affected

The OpenJDK advisory lists the 17, 21, 25 and 27 branches up to 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3; Calif places the start at 17.0.6. Java 8 and 11 are not marked as affected. All builds derived from OpenJDK are concerned (Temurin, Corretto, Zulu, Red Hat, Microsoft…), but only on x86-64 processors with AVX-512 VBMI: Intel Xeon from Ice Lake onwards and AMD Zen 4 or newer, which covers many recent cloud instances. ARM64 is not affected. Calif says it obtained code execution without authentication, in the default configuration, on Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. A trigger program is public; the full exploit chains are held back for now. No attack in the wild had been reported on 17 November.

What to do now

  1. Check the processor: grep -o -w avx512vbmi /proc/cpuinfo | sort -u. No output means this flaw does not apply to that host.
  2. List every Java runtime, including those bundled with applications and container images: find / -type f -path '*/bin/java' 2>/dev/null, then java -version for each.
  3. Install the 17 November update from your distribution or vendor, rebuild the images, restart the services. Expose Jira, Confluence, Jenkins and Keycloak first.
  4. Until then, start the JVM with -XX:-UseBASE64Intrinsics (or -XX:UseAVX=2, x86-64 only: an ARM JVM refuses to start with it).
  5. Watch for unexpected JVM crashes (hs_err_pid*.log files) and unknown Java processes.

Our take

Java is rarely in the patch inventory: it hides inside applications, appliances and images. A flaw that depends on the CPU model is a reminder that the same image can be safe on one host and exposed on another. Knowing exactly which runtime runs where is what makes a same-day fix possible.

Sources

How we choose, verify and write our analyses →

Is your own server exposed? Run a free check — public information only, no intrusion:

Check a server Check a website

Worried your servers are exposed? Our team audits, patches and monitors Linux and cloud infrastructure 24/7.

Talk to an expert Our managed server services →