CVE-2026-114938, dubbed Java4Shell, is a memory-corruption defect in OpenJDK’s hardware-accelerated Base64 decoder that can crash the JVM, expose heap memory and, under application-specific conditions, enable remote code execution. Oracle and OpenJDK released fixes on November 17; users should update to a vendor-confirmed fixed runtime or, if they cannot patch immediately, disable the vulnerable Base64 intrinsic and restart affected JVMs.
How Java4Shell works
OpenJDK uses AVX-512 instructions to accelerate Base64 decoding on supported x86-64 CPUs. In the vulnerable routine a malformed Base64 padding value can cause an output-length calculation to underflow, producing an invalid write that can overwrite memory beyond the decoder’s output buffer. The Java code may later reject the malformed input, but the memory corruption can already have occurred.
The reported exploitation path requires several conditions: a vulnerable runtime build with the intrinsic enabled, a compatible x86-64 processor exposing the required AVX-512 features, and attacker-controlled Base64 data reaching the decoder. Calif lists Intel Xeon Ice Lake and later server families and AMD Zen 4 or later as processors that meet those requirements; ARM64 systems are not affected by the reported x86-64 path.
A remote attacker could supply the triggering data via any application feature that decodes Base64 (authentication, token handling, file processing, etc.). Calif also described a client-side scenario in which a Java program connecting to a malicious server could be affected. Whether exploitation is possible before authentication, and whether it leads to RCE, depends on the application’s data flow and memory layout.
Scope, affected builds and demonstrations
Oracle lists affected builds including 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, and also affected GraalVM builds. OpenJDK’s matrix lists unpatched lines of Java 17, 21, 25 and 27. Standard Java 8 and 11 builds are not listed. Vendor builds and fix schedules vary; check the advisory for the runtime you use.
Calif reported pre-authentication RCE demonstrations in default configurations of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate. Calif also reported post-authentication demonstrations in Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker. Calif demonstrated RCE in specific Java applications but noted there is no single exploit that applies to every Java service; the public proof of concept demonstrates memory corruption but that alone does not prove universal remote RCE.
Severity, exploitation status and threat intelligence
Oracle and the JDK rate the flaw 8.1 (High) under CVSS 3.1; NVD carries the same v3.1 score. Calif assigns CVSS 4.0 a 9.2 score. Bitsight CTI assigns a DVE score of 9.99/10 (Critical), up from 5.75 on November 1; DVE models the likelihood of exploitation over a 90-day period based on threat intelligence.
Public reporting shows no confirmed widespread exploitation in the wild. VulnCheck said the flaw was not known to be exploited in the wild while reporting that it had a full RCE exploit available to its customers. Bitsight CTI did not flag in-the-wild exploitation, Metasploit use, or ransomware/APT association. Calif said it was withholding product-specific exploit chains. CIRCL reported that the Canadian Centre for Cyber Security had no known active exploitation in its November 17 alert.
Mitigation and recommendations
Apply vendor patches: update to a vendor-confirmed fixed runtime. If immediate patching is not possible, temporarily disable the vulnerable Base64 intrinsic and restart affected JVMs.
Calif disclosed Java4Shell on November 17. Exposure depends on runtime build, CPU features, JVM configuration and whether attacker-controlled Base64 data reaches the decoder; assess those factors when prioritizing updates and mitigations.

