Java4Shell: Pre-Authentication RCE in the OpenJDK Base64 Decoder (CVE-2026-114938)
Source report →On November 17, 2026, the security firm Calif disclosed Java4Shell (CVE-2026-114938), a memory-corruption vulnerability in OpenJDK's Base64 decoder that it rates 9.2 (Critical) under CVSS v4.0. A remote attacker with no credentials can overwrite heap memory, read heap memory, and reach remote code execution. The OpenJDK Vulnerability Group published an advisory the same day that lists the CVE in the hotspot/compiler component with a CVSS v3.1 score of 8.1, affecting Java 17, 21, 25 and 27, and Oracle released a patch.
To decode Base64 faster, OpenJDK HotSpot uses an intrinsic written with AVX-512 VBMI instructions on supported x86-64 processors, which is used once the decoding routine has run often enough to be compiled by the C2 JIT compiler. The bug is in the assembly code that handles the final characters of the input. When the remaining input is a padded tail shorter than one complete block, the output length is computed as zero and then decremented for the padding, so it underflows to a negative value and the store mask becomes a full 64-byte write. For a 65-character input of 64 `A` characters followed by a single `=`, OpenJDK allocates a 50-byte result array and the routine writes 64 bytes starting at offset 48, which sends 62 bytes past the end of the array. Java then rejects the input with an exception, after neighboring objects may already be corrupted. On OpenJDK 17 the trigger is 128 `A` characters followed by `=`, because the length threshold to reach the code path is higher.
The out-of-bounds bytes are fixed, and only the landing position of the write is controllable. Calif describes overwriting the length of a neighboring buffer, which turns the fixed write into a chosen-value linear write, and then corrupting a second array's length so that heap memory is copied back in a response. It calls this disclosure primitive JavaBleed and states that the leaked heap may hold PII, private keys, other secret keys and tokens. From these two primitives the chain escalates to arbitrary writes that reach the Code Cache and JVM hooks for code execution. The technique depends on heap grooming with sprayed objects and retries, and an incorrect placement can crash the JVM, after which the attacker can in many instances try again. There is no universal exploit: each target needs an application-specific profile, and the attack is sensitive to network round-trip time and jitter. Some grooming profiles need partial request bodies to reach the application, which a proxy that waits for the complete body prevents, but request buffering is not a general mitigation.
Calif reports demonstrating remote code execution against widely deployed Java applications in their default configurations. Before authentication: Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. After authentication: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. It describes both lists as non-exhaustive and also reports code execution in sample applications built on Apache Struts and Spring Boot. Ordinary features such as authentication and file uploads can expose the vulnerable decoder. A client-side exploit also exists: a Java program that opens a TLS connection to a malicious server can be compromised even if it exposes no service of its own. Calif published a self-contained proof of concept that triggers the overwrite inside its own array, and it is withholding the application-specific exploits until users have had a chance to upgrade.
Java4Shell affects OpenJDK from version 17.0.6 up to the builds that precede the November 17, 2026 fix: the OpenJDK advisory lists 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3 and earlier as affected, and later builds carry the fix. Calif lists the distributions built from OpenJDK as also vulnerable: Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle OpenJDK, Oracle Java SE and Oracle GraalVM for JDK. Oracle's advisory lists the supported versions affected as Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, and Oracle GraalVM Enterprise Edition 21.3.20.0.3. Oracle names supported versions only, so older builds of the same lines are not listed there. The vulnerable code is hardware-specific and requires an x86-64 processor with AVX-512 VBMI support. Calif names these mainstream CPU families as meeting the requirement: Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD EPYC and Ryzen on Zen 4 or newer. ARM64 processors are not affected. On Linux, a processor meets the requirement when its CPU flags include all four of `avx512f`, `avx512bw`, `avx512vbmi` and `bmi2`.
Vega's review of the OpenJDK source agrees with this scope. The accelerated decoder is absent in the 17.0.5, 11.0.25 and 8u432 sources, and present in the 17.0.6, 17.0.17, 21.0.5 and 25 sources. Java 17 takes the accelerated path only for inputs longer than 128 bytes, while Java 21 and 25 take it for inputs of 32 bytes or more, which is consistent with the longer trigger on Java 17.
The remediation is to update: OpenJDK released a security advisory and Oracle released its patch on November 17, 2026. Java4Shell can also be mitigated by starting OpenJDK with `-XX:-UseBASE64Intrinsics`, which disables hardware-accelerated Base64 encoding and decoding, or with `-XX:UseAVX=2`, which disables AVX-512. The second flag applies only to x86-64 hosts, because OpenJDK on ARM does not recognize it and fails to start. The write-up describes no activity after code execution. The detections listed with this brief cover what would follow code execution inside the Java process: that process spawning command interpreters, discovery commands, download tools or installers.
Detections (10)
Enable detections →Connect your environment for suggestions and queries personalized to your security telemetry.
- Oracle EBS Post-Exploitation Linux Reconnaissance via SentinelOne
- PowerShell Download Cradle Spawned by Web Server Process
- Msiexec Installing MSI from Web Server Parent
- SSHPass Credential Spraying Across Internal Hosts
- Shell Reverse Connection via Dev TCP Redirection
- Named Pipe Reverse Shell via mkfifo
- Netcat or Socat Listener with Command Execution
- Scripting Interpreter Reverse Shell
- Download Tool Spawned by a Java Server Process on Linux