---
title: "CVE-2026-114938—Java4Shell RCE Vulnerability Gives New Meaning to “Run Anywhere”"
date: "2026-11-18T12:50:49+00:00"
url: "https://checkmarx.com/zero-post/cve-2026-114938-java4shell-rce-vulnerability-gives-new-meaning-to-run-anywhere/"
description: "cve-2026-114938 Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE"
---

# CVE-2026-114938—Java4Shell RCE Vulnerability Gives New Meaning to “Run Anywhere”

## **TL; DR–How to Defend**

CVE-2026-114938, nicknamed Java4Shell and given a CVSS 4.0 score of 9.2, has recently been identified in Java OpenJDK’s base64 mechanism. **It affects Java 17.0.6 and later, as well as 21, 25, and 27, on x86-64 servers with AVX-512 VBMI**, a feature common on widely used Intel and AMD hardware. When the conditions are met, there is a **high likelihood of resulting in unauthenticated remote code execution on most Java servers**. Patch now.

On affected builds, we recommend updating OpenJDK to versions newer than 17.0.6 to 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1 immediately. Containerized images need rebuilding rather than directly patching the host, as certain OpenJDK images pin the version.

## **Introduction**

Java, an extremely popular object-oriented programming language with a presence in the backends of roughly 90% of Fortune 500 companies, has one of its most popular implementations, OpenJDK, suffer from a major vulnerability in its base64 decoder mechanism. OpenJDK is the most used Java implementation on servers and PCs, so many builds are likely to be affected worldwide.

## **What Happened**

The vulnerability, CVE-2026-114938, exploits OpenJDK’s base64 decoding mechanism. It was disclosed to Oracle by Calif.

Base64 is an extremely popular encoding mechanism used to normalize any input, from bytes to special characters, into a single string of a-zA-Z0-9 characters, allowing it to be safely transmitted inside data containers such as JSON, safely written as data into a token, normalize random cryptographic bytes into a transmittable format, and more.

Base64 is at the core of many mechanisms, for example, storing binary data as readable strings, or as part of authentication such as in JSON Web Tokens (JWT). Because it is so ubiquitous in internet-facing mechanisms that require no authentication, being able to trigger code execution from a Base64 decoding action is basically a skeleton key to a vast majority of Java systems, and combined with Java’s prevalence in major organizations, that makes it an attacker’s wet dream.

The vulnerability exploits the base64 decoder, and specifically the tail end of the base64—base64 relies on padding bytes it encodes when their length is not divisible by 3, by padding an additional “=” or “==”, which causes the length of the string being decoded to be divisible by 4. When an additional stray “=” padding is added, decoding will fail, but before it happens, the optimization process for AVX-512 VBMI instructions already writes past the end of the output buffer. This is rejected by Java correctly, but the adjacent memory has been corrupted, which could lead to arbitrary code execution with the proper heap grooming.

## **Who is Vulnerable**

Users of Java OpenJDK running on x86-64 CPUs with AVX-512 VBMI are vulnerable, starting from version 17.0.6.

The OpenJDK implementation is the most commonly used Java implementation on servers and personal computers, making most, if not all, Java deployments in a given organization rely specifically on it. The vulnerable code was introduced in a January 2023 release to optimize performance on certain key functionality in Java.

The vulnerability exploits an optimization around instructions specific to x86-64 systems; while other systems such as ARM64 may not be similarly vulnerable, it is still highly recommended to update OpenJDK to its latest versions.

| **Product** | **Affected Versions** | **Fixed Versions** |
|---|---|---|
| OpenJDK | 17.0.6 and later; 21.x; 25.x; 27.x | 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1 |
| Oracle Java SE | 17.0.6 and later; 21.x; 25.x; 27.x | 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1 |
| Oracle Java SE 8 Performance Pack | 8u511b33-perf | 8u513-perf |
| Oracle GraalVM for JDK | 17.0.6 and later; 21.x | 17.0.21.1, or 21.0.13.1 |
| Oracle GraalVM Enterprise Edition | 21.x | 21.3.20.1 |

The following Java distributions built from OpenJDK are also known to be affected, but this list is not exhaustive.

- Amazon Corretto

- Eclipe Temurin

- Microsoft Build of OpenJDK

- Azul Zulu

- BellSoft Liberica

- SAP SapMachine

- Red Hat OpenJDK

**You are not affected if:**

- Running OpenJDK or Oracle Java SE on branch 8.x or 11.x (only Oracle Java SE 8 Enterprise Performance Pack is affected).

- Running the Java Runtimes on ARM64 CPUs.

- Your x86-64 CPU lacks AVX-512 VBMI (the JVM must see avx512f, avx512bw, avx512vbmi and bmi2).

- The Base64 intrinsic (`-XX:-UseBASE64Intrinsics)` or AVX-512 is disabled (`-XX:UseAVX=2` to disable).

## **Mitigations**

Users are encouraged to update OpenJDK to 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1. For Oracle products, check the table above. Other vendors with their own OpenJDK distributions are releasing their fixes on their own schedules. Check each vendor’s security advisory and release notes for updates.

Containerized images need rebuilding with the safe versions rather than directly patching the host, as certain OpenJDK images pin the version.

In case upgrading isn’t possible, the following mitigations have been proposed by the researchers at Calif, vendors such as RedHat, to do either of the following:

- Use the flag -XX:-UseBASE64Intrinsics to disable hardware-accelerated base64 – since this targets the vulnerable mechanism rather than the hardware feature, it is the recommended form of mitigation.

- Use the flag -XX:UseAVX=2 to disable the AVX-512 instruction entirely. This will disable the instruction which may affect performance. Don’t apply on architectures other than x86-64 such as ARM, or it will cause OpenJDK to fail to start.

## **Part of a Wider Oracle Security Release**

The new releases of OpenJDK and Oracle Java SE not only patch CVE-2026-114938 but also 10 other CVEs affecting release lines from 8 to 27, with CVSS3.1 scores ranging from 3.7 to 7.5, making Java4Shell the most critical one with 8.1 (CVSS3.1). All the vulnerabilities in this release may be remotely exploited without any authentication.

**Note**: Oracle’s release is not limited to Java. The same pre-release announcement lists 652 new security patches across Oracle products, including Oracle WebLogic Server, Oracle MySQL, and Helidon.

You can find more details in [Oracle’s official advisory](https://oracle.com/security-alerts/cspunov2026.html).

## **Conclusions**

Make sure to update OpenJDK on all systems to its latest versions, where possible, and otherwise apply the suggested mitigations as a stopgap until an update can be performed.

Another rough week for organizations and maintainers everywhere, with another critical vulnerability in a core technology that is a backbone of the industry being discovered by AI. At this point, it seems almost everybody is affected by one of these deadly vulnerabilities.

Remain vigilant and update critical security patches as soon as they are made available.

## **References**

44. [Oracle patch notes](https://oracle.com/security-alerts/cspunov2026.html)
45. [Original release notes introducing the vulnerable feature](https://oracle.com/java/technologies/javase/17-0-6-relnotes.html)
46. [Calif’s disclosure blog](https://calif.io/java4shell)
