A critical memory-corruption vulnerability, designated CVE-2026-114938 and dubbed Java4Shell, has been identified within the OpenJDK Base64 decoder. The flaw, which carries a CVSS v4.0 severity rating of 9.2, stems from handwritten assembly code designed to accelerate Base64 decoding using AVX-512 instructions. Because Base64 encoding is frequently used for login headers, authentication tokens, and file uploads, the vulnerability can be triggered before a user has successfully authenticated, potentially leading to remote code execution (RCE) or the unauthorized reading of sensitive data from the Java heap.
The vulnerability affects OpenJDK-based builds from version 17.0.6 onward, including versions 21, 25, and 27, as well as specific Oracle Java SE 8 Enterprise Performance Pack releases. For the flaw to be exploitable, the Java runtime must be running on x86-64 processors that support AVX-512 VBMI instructions. This hardware requirement includes Intel Xeon processors from the Ice Lake generation through Granite Rapids, as well as AMD EPYC and Ryzen processors based on the Zen 4 architecture or newer. Systems running on ARM64 or x86-64 hardware lacking these specific instructions are not susceptible to this exploit.
Researchers have confirmed that the vulnerability can be exploited against default installations of several widely used enterprise products, including Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate. Additionally, authenticated users may be able to trigger the flaw in applications such as Apache Kafka, Apache Solr, Elasticsearch, Gerrit, and Netflix Spinnaker. The vulnerability also extends to client-side Java programs, which could be compromised simply by establishing a TLS connection to a malicious server.
While there have been no confirmed reports of exploitation in the wild as of November 17, 2026, the Cybersecurity and Infrastructure Security Agency (CISA) has issued an urgent alert recommending immediate patching. Security experts warn that because the root cause and exploitation techniques have become public, organizations should not rely on the current lack of active attacks as a justification for delay. The vulnerability is considered particularly dangerous because it resides within the Java runtime itself, meaning that services can be exposed regardless of whether the individual application code is secure.
The primary remediation is to update the Java runtime to a patched version. Oracle released fixes on November 17, 2026, and other OpenJDK vendors, such as Amazon with its Corretto distribution, have begun rolling out updates. Organizations are advised to verify their specific vendor advisories to confirm that the installed build addresses CVE-2026-114938. It is critical to note that simply updating the package is insufficient; every Java process must be restarted for the patch to take effect.
For environments where immediate patching is not feasible, a temporary workaround is available through the use of specific Java Virtual Machine (JVM) startup flags. The preferred method is to set -XX:-UseBASE64Intrinsics, which disables the vulnerable fast Base64 decoder and forces the application to use the standard decoder. Alternatively, setting -XX:UseAVX=2 will disable the broader set of processor optimizations that include the vulnerable code, though this approach carries a higher performance penalty and is not compatible with ARM-based systems.
When assessing risk, administrators must account for the fact that many applications and container images bundle their own Java runtimes, which may not be updated by standard operating system maintenance. Furthermore, while a system may currently reside on hardware that does not meet the vulnerability criteria, future infrastructure changes, such as instance resizing or migration to newer hardware, could inadvertently expose the system. Consequently, CISA and security researchers advise organizations to prioritize patching internet-facing identity, CI/CD, and collaboration systems, and to ensure that every system has a designated owner and a clear remediation deadline.



