A critical vulnerability in OpenJDK’s Base64 decoder could, in the worst-case scenario, allow attackers to take control of widely used enterprise applications.
Oracle and the OpenJDK project have patched a serious security vulnerability in the Java Runtime Environment. Researchers at security firm Calif, who discovered the flaw, have named it Java4Shell, drawing a parallel with the notorious Log4Shell vulnerability disclosed in 2021. The vulnerability is officially tracked as CVE-2026-114938.
According to Calif, the flaw allows attackers to compromise popular enterprise applications such as Jira, Jenkins and Keycloak without prior authentication when running with default configurations. A coordinated disclosure had originally been planned, but after details leaked ahead of schedule, Calif published its findings on November 17.
Bug in the Base64 Decoder’s AVX-512 Code Path
The vulnerability stems from a memory corruption bug in a routine OpenJDK uses to decode Base64-encoded data. Specifically, it affects the optimized code path for x86-64 processors supporting the AVX-512 VBMI instruction set extension. Malformed Base64 strings can cause the routine to write beyond the end of its output buffer, overwriting adjacent heap data before Java even recognizes the input as invalid.
With carefully crafted input, the memory corruption could expose sensitive information or enable arbitrary code execution, Calif explains. The affected heap memory could contain personal data, secret keys or authentication tokens.
Jira, Confluence and Jenkins: Takeover Without Authentication
In initial tests, the researchers achieved unauthenticated remote code execution (RCE) on Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate, all running with default settings. With valid credentials, they also managed to execute code on Apache Kafka brokers, Solr, Elasticsearch, Gerrit and Spinnaker. Calif emphasizes that neither list is exhaustive. The researchers also compromised sample applications built with Apache Struts and Spring Boot. The vulnerable decoder can be reached through everyday application functions, including login processes and file uploads.
Even client applications are at risk. An exploit forwarded to Calif by security researcher samczsun demonstrates that a Java application can be compromised simply by establishing a TLS connection to an attacker-controlled server, even if the application does not expose any services of its own. However, there is no universal exploit. The steps required to carry out an attack depend on how an application uses Base64, Calif acknowledges. The proof of concept published by Calif demonstrates memory corruption but does not achieve code execution. The company plans to release product-specific exploit chains only after users have had sufficient time to apply the necessary updates.
Which Versions Are Affected?
OpenJDK versions 17.0.6 and later are vulnerable, as are distributions based on OpenJDK, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, Red Hat OpenJDK and Oracle Java SE. The OpenJDK advisory identifies Java 17, 21, 25 and 27 as affected.
However, exploitation requires x86-64 hardware with AVX-512 VBMI support. This includes, for example, Intel Xeon processors from the Ice Lake generation onward and AMD chips starting with Zen 4. Systems running ARM64 processors are not vulnerable.
The severity assessments differ. Calif assigns the vulnerability a CVSS 4.0 score of 9.2. Oracle rates it 8.1 under CVSS 3.1. While Oracle classifies the flaw as remotely exploitable without authentication, it considers the attack complexity high.
Patches Not Yet Available for All Distributions
Oracle addressed the vulnerability in its November Critical Security Patch Update, which fixes a total of eleven vulnerabilities in Java SE. Users of other Java distributions, however, may have to wait for patched builds from their respective vendors, Endor Labs notes. As of November 17, the fix had not yet reached the public update repositories for OpenJDK 17, 21 and 25.
The US Cybersecurity and Infrastructure Security Agency (CISA) is urging organizations to apply patches immediately, prioritizing systems accessible from the internet. Administrators should also actively search for Java installations embedded in third-party software, containers and appliances. These installations often do not appear as separate entries in asset inventories and could otherwise go unnoticed.
(Editorial Team)