The Cybersecurity and Infrastructure Security Agency urged organizations on November 17 to patch immediately against a critical memory-corruption vulnerability in Java itself. Tracked as CVE-2026-114938 and nicknamed Java4Shell, the flaw sits in the Base64 decoder of the HotSpot Java Virtual Machine, part of the Java Development Kit. Security firm Calif, which discovered and reported the bug, says a specially crafted Base64 string that reaches the decoder can crash the JVM or enable unauthenticated remote code execution.
The defect is not in an application or a library. It is in hand-written x86-64 assembly that HotSpot uses to speed up Base64 decoding with AVX-512 VBMI instructions, in a routine reached through java.util.Base64.Decoder. According to Calif, a malformed input of 64 letter A characters followed by a single equals sign can write 62 bytes past the end of its output buffer, corrupting heap memory. That corruption can also leak sensitive data held in memory, in addition to crashing the process or giving an attacker control of it.
Three conditions must line up for a system to be exposed. The runtime must be an unpatched OpenJDK-based build from 17.0.6 onward, covering the Java 17, 21, 25 and 27 lines, and the processor must be an x86-64 chip with AVX-512 VBMI support. That includes Intel Xeon processors from Ice Lake through Granite Rapids and AMD EPYC and Ryzen processors from Zen 4 onward. ARM64 systems are not affected, and standard OpenJDK 8 and 11 do not contain the vulnerable code path, although Oracle lists its Java 8 Enterprise Performance Pack build 8u511b33-perf as affected.
Calif says it demonstrated pre-authentication remote code execution against default installations of Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate. Those are exactly the kinds of identity, collaboration and build systems that sit at the center of enterprise networks, which is why CISA moved the same day. Calif researcher Quang Luong found the flaw with help from an AI coding tool, in what the firm describes as about an hour of work, and built a first application-specific exploit about two hours later. Oracle credits Calif researchers Albert Yang and Quang Luong in its November update.
Scoring reflects both the reach and the difficulty. Calif rates Java4Shell 9.2 under CVSS 4.0, in the critical range, while Oracle and the OpenJDK advisory rate it 8.1 under CVSS 3.1, with high attack complexity and no authentication required. As of November 18, no vendor or agency had reported exploitation in the wild, and CISA had not added the flaw to its Known Exploited Vulnerabilities catalog. Calif is withholding its product-specific exploits while users patch, but the underlying technique is now public, and other researchers expect probing to increase.
Oracle released fixed builds on November 17 as part of its November Critical Security Patch Update, which covered 655 vulnerabilities across its portfolio, including 11 fixes in Java SE. The replacement Java SE builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Amazon had also released a fixed Corretto build, while several other distributions, including Red Hat builds, had not yet shipped fixes as of November 18. Where patching must wait, administrators can start affected JVMs with the flag -XX:-UseBASE64Intrinsics, which disables the accelerated Base64 routines that contain the bug. CISA also advises patching internet-facing systems first, hunting for Java runtimes bundled inside third-party software, container images and appliances, restricting unauthenticated access, and validating Base64 input at the application boundary.