A critical memory corruption vulnerability, identified as CVE-2026-114938 and nicknamed Java4Shell, has been disclosed in the OpenJDK platform. The flaw resides within the Java Base64 decoding mechanism, specifically affecting a performance optimization shortcut designed for certain x86-64 processors. By sending a specially crafted Base64 string, an attacker can trigger a buffer overflow, writing data beyond allocated memory boundaries. This can lead to the unauthorized disclosure of sensitive information—such as cryptographic keys or session tokens—or enable remote code execution on the target server.
The vulnerability was officially patched by Oracle as part of its November 2026 Critical Security Patch Update (CSPU) released on November 17, 2026. The issue was reported to Oracle by researchers Quang Luong and Albert Yang. While Oracle has assigned the vulnerability a CVSS 3.1 score of 8.1, noting that the attack complexity is high, some researchers have argued for a higher severity rating of 9.2 under the CVSS 4.0 framework.
A key factor in the exploitability of Java4Shell is the underlying hardware. The vulnerability only manifests on x86-64 processors that support the AVX-512 VBMI instruction set. This includes Intel Xeon processors from the Ice Lake, Sapphire Rapids, Emerald Rapids, and Granite Rapids families, as well as AMD processors based on the Zen 4 architecture or newer. Systems utilizing ARM64 processors are not affected. On Linux environments, the vulnerability is present if the processor reports the avx512f, avx512bw, avx512vbmi, and bmi2 flags.
The affected software includes various OpenJDK-based distributions, such as Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, and Red Hat OpenJDK. Regarding specific Java versions, the OpenJDK Vulnerability Group has identified the Java 17, 21, 25, and 27 release lines as vulnerable. Oracle has confirmed that its Java SE 8 Enterprise Performance Pack, as well as specific builds of Java SE and GraalVM, are impacted.
Security researchers have demonstrated that the flaw can be triggered in several widely used enterprise applications, including Atlassian Jira, Atlassian Confluence, Jenkins, Keycloak, JFrog Artifactory, and PingFederate, often without requiring authentication. Other applications, such as Apache Kafka, Apache Solr, Elasticsearch, Gerrit, and Spinnaker, have also been identified as potentially exploitable, though sometimes requiring an authenticated session. Additionally, researchers have indicated that client-side Java programs may be compromised if they connect via TLS to a malicious server, even if the program does not host any services itself.
As of November 17, 2026, there have been no confirmed reports of Java4Shell being exploited in the wild, and it does not currently appear on the Cybersecurity and Infrastructure Security Agency’s (CISA) Known Exploited Vulnerabilities catalog. While a proof-of-concept that triggers the bug has been made public, researchers have stated they are withholding specific exploit code for individual applications for the time being.
Users are advised to check with their specific Java distribution vendor for the availability of patched builds. Because the vulnerability is rooted in the OpenJDK codebase, applying the latest security updates provided by the respective vendor is the primary mitigation strategy. Organizations should prioritize patching systems running on the specified Intel and AMD processors, as these are the only environments where the vulnerable performance shortcut is active.




