A critical flaw designated Java4Shell has been discovered in OpenJDK, the open-source Java implementation, that enables unauthenticated attackers to execute arbitrary code on major enterprise platforms including Jenkins, Atlassian Jira, Confluence, and Keycloak. The vulnerability affects Java's hardware-accelerated Base64 decoding functionality and can lead to both information disclosure and remote code execution.
Java remains one of the world's most prevalent programming platforms, underpinning enterprise applications, web services, financial systems, and critical infrastructure. Because numerous applications rely on the same Java runtime environment, flaws in core Java components can cascade across many disparate systems.
The flaw is tracked as CVE-2026-114938 and stems from a memory-corruption bug in Java's Base64 decoder, which processes encoded data routinely used in authentication, file uploads, and network communications. Security researchers at Calif disclosed the vulnerability on Tuesday and assigned it a critical CVSS 4.0 score of 9.2, though Oracle rated it as High with a CVSS 3.1 score of 8.1.

The vulnerability impacts OpenJDK 17.0.6 and later versions, as well as Java distributions derived from the affected codebase, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, and Red Hat OpenJDK.
Exploitation mechanism
According to Calif researchers, specially constructed Base64 data can trigger the decoder to overwrite sections of Java memory, potentially enabling attackers to extract sensitive data or inject malicious instructions. The memory corruption can be initiated with just 64 consecutive "A" characters followed by an equals sign:
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Older OpenJDK 17 versions require 128 "A" characters before the equals sign to trigger the same condition.
The flaw only activates when using a hardware-accelerated decoding function available on specific x86-64 processors that support AVX-512 instructions. Researchers demonstrated successful remote code execution against multiple widely used Java applications operating with default settings.
Affected applications
Calif researchers successfully exploited the vulnerability in the following applications:
- Unauthenticated RCE: Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate
- Authenticated RCE: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker
The researchers also demonstrated exploitation against sample applications developed with Apache Struts and Spring Boot frameworks.
Calif noted that Java4Shell lacks a universal exploit; attackers must identify an application-specific method to deliver malicious Base64 data to the vulnerable decoder. Additionally, successful exploitation requires that the affected hardware-accelerated AVX-512 decoding function be utilized, which depends on x86-64 processors equipped with AVX-512 VBMI capabilities.
Discovery and AI involvement
Researcher Quang Luong at Calif discovered the vulnerability using OpenAI's Codex AI coding assistant during an audit of OpenJDK internals. According to the company, Luong identified the flaw in approximately one hour and developed an initial working exploit within two additional hours, with total AI usage costs under $200.
Calif states that AI agents also contributed to developing application-specific exploitation chains. The company has released a proof-of-concept demonstrating the memory corruption but has withheld the weaponized exploits used against enterprise applications.
Patches and mitigation
Oracle released patches for CVE-2026-114938 on November 17 as part of its November Critical Security Patch Update, which addressed 655 security vulnerabilities across its product lineup. The company urges customers to deploy available security patches immediately.
For organizations unable to update Java immediately, Calif recommends disabling the vulnerable hardware-accelerated Base64 functionality by launching OpenJDK with the -XX:-UseBASE64Intrinsics option.
Alternatively, administrators operating Java on x86-64 systems can use -XX:UseAVX=2 to disable AVX-512 instructions.
However, these workarounds represent temporary mitigations only. All developers should upgrade their Java runtimes to the latest version to fully address the vulnerability.