A critical remote code execution vulnerability affecting OpenJDK Java 17, 21, 25 and 27 has been reported under CVE-2026-114938, informally known as Java4Shell (also referred to as Java2Shell). The vulnerability is reportedly exploitable without authentication (in some cases) and has been assigned a preliminary CVSS v4.0 score of 9.2 (Critical).
The vulnerability was reported by Calif, which announced its discovery and the planned technical disclosure in this post on X.
With Java widely used across enterprise applications, backend services, and production environments, organizations should start identifying potentially affected Java deployments and prepare for remediation.
Affected and Fixed Versions
Java4Shell affects OpenJDK and Java SE in branches 17.x, 21.x, 25.x and 27.x
The following fixed versions were released -
17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1
Organizations must urgently inventory their Java applications, deployments, and internet-facing instances and update to one of the fixed versions mentioned above.
Java4Shell is the informal name given to CVE-2026-114938 by Calif, the security research firm that reported the vulnerability. In its announcement on X, Calif reported the discovery and later published the technical details following Oracle's November security patch release.
According to Calif, Java4Shell is a memory-corruption bug in the x86-64 intrinsic implementation of OpenJDK's Base64 decoder. When the decoder processes padded input (a stray = character), it miscalculates the store mask, causing an out-of-bounds heap write past the end of the output buffer. Calif says this can be leveraged for heap disclosure (Heartbleed-style) and for remote code execution.
In essence, any application that decodes externally-supplied Base64 content could be affected -
import java.util.Base64;
Base64.Decoder decoder = Base64.getDecoder();
decoder.decode(EXTERNAL_INPUT, ...)
The issue only affects x86-64 CPUs that support AVX-512 VBMI (ARM64 is not affected), and impacts OpenJDK 17.0.6 and newer as well as derivatives such as Temurin, Corretto and Oracle Java SE. Calif also claims that several popular Java-based products can be exploited this way, in some cases without authentication.
Yes. CVE-2026-114938 is already represented in JFrog Xray and JFrog Catalog.
Updating to one of the fixed versions is the best fix for Java4Shell.
If updating is not possible, the following mitigations are available (either one would deny exploitation of the vulnerability) -
- Start OpenJDK with
-XX:-UseBASE64Intrinsics - Start OpenJDK with
-XX:UseAVX=2