A critical heap out-of-bounds write vulnerability, tracked as CVE-2026-114938 and referred to as Java4Shell, has been identified in the HotSpot AVX-512 Base64 decoder. The flaw resides in the way the Java Virtual Machine (JVM) handles specific Base64-encoded inputs on x86-64 processors equipped with AVX-512 VBMI instructions. While researchers have demonstrated that this vulnerability can lead to pre-authentication remote code execution, there have been no confirmed reports of exploitation in the wild as of November 17, 2026.
The vulnerability affects a broad range of Java versions, specifically Oracle Java SE and OpenJDK versions 17 (from 17.0.6), 21, 25, and 27, as well as Oracle GraalVM and the Oracle Java SE 8 Enterprise Performance Pack. Older versions, such as those prior to 17.0.6, are not affected because they lack the specific AVX-512 decoder implementation. The issue stems from an integer underflow in the stub handling of Base64 tails, which can result in a 62- or 63-byte write past the destination array on the Java heap.
For an environment to be susceptible, four conditions must be met simultaneously: the system must be running on an x86-64 CPU supporting AVX-512 VBMI (such as Intel Ice Lake or newer, or AMD Zen 4 and later); the JVM must be a vulnerable version; the JVM must have the default settings of UseAVX=3 and UseBASE64Intrinsics=true enabled; and an attacker must be able to supply Base64-encoded input to the basic or URL decoder. Vulnerable applications identified by researchers include Keycloak, Jira, Confluence, Artifactory, Jenkins, PingFederate, Kafka, Solr, Elasticsearch, Gerrit, and Spinnaker.
Oracle released patches for the affected builds on November 17, 2026. Users are urged to upgrade to the latest versions: 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1. It is important to note that simply having a current version number is insufficient if the build predates the fix; for example, certain distribution-specific packages, such as those from Ubuntu or Oracle Linux, may remain vulnerable even if they appear up-to-date.
For organizations unable to apply the official patches immediately, a temporary mitigation is available. By starting the JVM with the flag -XX:-UseBASE64Intrinsics, administrators can disable the problematic vector instructions. This effectively forces the JVM to use the scalar path, which is not susceptible to the heap write issue. This change requires a JVM restart to take effect.
The technical root cause involves the L_finalBit logic in the Base64 decoder stub. Before the fix, specific tail lengths of 1 to 3 characters ending in an equals sign could result in an incorrect output size calculation, leading the system to write data to memory incorrectly. The patch, identified as JDK-8393212, introduces a check that forces these smaller tails to be processed by the scalar path, preventing the underflow.
CISA has issued an alert regarding this vulnerability, emphasizing the need for immediate remediation. While the vulnerability has been classified as a potential remote code execution vector, unsuccessful exploitation attempts are expected to result in a denial-of-service condition on the affected endpoint. Administrators can verify their exposure by querying the JVM for CPU capabilities using the command java -Xlog:os+cpu, rather than relying on host-level OS reporting.






