Oracle and other OpenJDK distributors released fixes on November 17 for CVE-2026-114938, a memory-corruption flaw nicknamed Java4Shell. Researchers at security firm Calif used it to achieve pre-authentication remote code execution in default configurations of products including Jira, Jenkins and Keycloak, and CISA urged Java users to patch immediately.
How the Java4Shell Bug Corrupts Memory in OpenJDK’s Base64 Decoder
CVE-2026-114938 sits in OpenJDK’s hardware-accelerated Base64 decoder. When the decoder receives malformed input, the optimized routine writes past the end of its output buffer and corrupts neighboring heap memory before Java rejects the input. The trigger is trivial: 64 “A” characters followed by an “=” sign, or 128 for older OpenJDK 17 builds.
The flaw can also leak memory in a way that resembles Heartbleed. Calif calls that capability JavaBleed, and says it can expose personal data, secret keys and tokens. A Java client can be hit as well when it connects over TLS to an attacker-controlled server, according to an exploit shared by researcher samczsun.
Affected Java Versions and the AVX-512 VBMI CPU Requirement
Only x86-64 processors that support AVX-512 VBMI instructions are affected, and ARM64 is not. Standard Java 8, Java 11 and Java 17.0.0 through 17.0.5 do not contain the vulnerable decoder. The affected builds include Java 17 from 17.0.6 through 17.0.21, Java 21 through 21.0.13, Java 25 through 25.0.5, Java 27 through 27.0.1, and the Java 8 Performance Pack build 8u511b33-perf. Oracle also lists affected GraalVM products.
The exposure spans every major distribution built on OpenJDK: Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK, along with the applications that run on them.
Calif Says OpenAI Codex Found the Flaw in About One Hour
Researcher Quang Luong of Calif found the bug using OpenAI’s Codex coding assistant. Calif says it took about one hour to find the flaw and two more hours to build a first working exploit, at a cost of under $200 in AI usage. Calif says the bug’s details leaked before coordinated disclosure.
Pre-Auth RCE Shown Against Keycloak, Jira, Confluence, Artifactory and Jenkins
Calif demonstrated pre-authentication remote code execution in default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. It also showed authenticated code execution against Apache Kafka Broker, Solr, Elasticsearch, Gerrit and Spinnaker, plus sample Apache Struts and Spring Boot applications. Calif says neither list is exhaustive.
Why No Universal Java4Shell Exploit Exists Yet
Each application needs its own route for delivering the malicious Base64 data to the decoder. HTTP Basic credentials, SAML artifacts, CSRF tokens and MIME encoded words can all reach it. Calif published a proof of concept that demonstrates memory corruption only, and is withholding weaponized, product-specific exploit chains until organizations have patched.
VulnCheck says crashing a vulnerable JVM is easy once an attacker finds a reachable entry point. The firm says it built a full RCE exploit, but that code execution requires heap-layout manipulation and an ASLR leak specific to each target. VulnCheck does not expect easy, widespread exploitation. Cisco Talos and SentinelOne have also published analyses.
Severity Scores Diverge and Bundled Runtimes Complicate Java4Shell Patching
The two scoring bodies disagree on severity. Calif rates CVE-2026-114938 at CVSS 4.0 9.2, which is critical. Oracle rates it CVSS 3.1 8.1, which is high, citing high attack complexity and no authentication requirement. Oracle did not single the flaw out in its advisory, which came as part of its November Critical Security Patch Update. No in-the-wild exploitation has been reported.
Patching is more involved than updating a single system JDK. Java runtimes bundled inside products and container images may remain vulnerable even after the system JDK is updated, so administrators need to check each application. Oracle’s November 17 advisory lists fixes, and each OpenJDK distributor ships a matching fixed build. Talos urged organizations to adopt the fixed Java versions.
The practical exposure depends on three factors: the CPU type, the Java build, and the per-application exploit work an attacker must complete. That limits the near-term risk, but the reach of the affected products, which include identity, source-control and build infrastructure, means the stakes for any successful chain are high.
