A critical OpenJDK vulnerability dubbed Java4Shell could allow unauthenticated attackers to execute code remotely in widely used enterprise applications, including Jenkins, Atlassian Jira, Confluence and Keycloak. Tracked as CVE-2026-114938, the flaw affects Java’s hardware-accelerated Base64 decoder and can cause memory corruption, potentially exposing sensitive data or enabling remote code execution.
Java is one of the world’s most widely used programming platforms, powering enterprise applications, web services, financial systems and critical business infrastructure. Because many applications rely on the same Java runtime, vulnerabilities in core Java components can affect a broad range of otherwise unrelated products.
Java4Shell vulnerability affects OpenJDK Base64 decoding
California security researchers at Calif disclosed the vulnerability on Tuesday. Oracle assigned it a CVSS 4.0 score of 9.2 and a CVSS 3.1 score of 8.1, which places the issue in the High-severity category under the older scoring system.
Java4Shell affects OpenJDK 17.0.6 and later, along with Java distributions built from the affected code. Impacted distributions include Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK.
The vulnerability results from a bug in Java’s Base64 decoder, which processes encoded data commonly used in authentication, file uploads and network communications. According to Calif, specially crafted Base64 input can cause the decoder to overwrite parts of Java’s memory, allowing an attacker to disclose sensitive information or execute malicious code.
Researchers said that 64 A
characters followed by an equal sign can trigger memory corruption:
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
Older OpenJDK 17 versions require 128 A
characters followed by an equal sign.
Enterprise applications vulnerable to remote code execution
The flaw only affects Java’s hardware-accelerated decoding feature on certain x86-64 processors that support AVX-512 instructions. Despite that limitation, researchers were able to exploit the vulnerability for remote code execution against several widely used Java applications running in their default configurations.
- Unauthenticated RCE: Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate.
- Certified RCE: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker.
Calif also exploited the issue in sample applications built with the Apache Struts and Spring Boot frameworks.
However, the researchers said there is no general-purpose exploit for Java4Shell. An attacker would need to find an application-specific method for delivering malicious Base64 data to a vulnerable decoder.
The vulnerability also requires the affected hardware-accelerated AVX-512 decoding path, which depends on an x86-64 processor supporting AVX-512 VBMI instructions.
AI assistant helped identify the flaw
According to Calif, researcher Quang Luong discovered the vulnerability while conducting an internal OpenJDK audit with help from OpenAI’s Codex AI Coding Assistant.
Researchers said Luong identified the flaw in about an hour and created an initial working exploit within another two hours, at a total AI cost of less than $200. The company said the AI agent also helped develop additional application-specific exploit chains.
Calif has published a proof of concept demonstrating memory corruption, but not a weaponized exploit targeting the affected enterprise applications.
Oracle releases a patch
Oracle released a patch for CVE-2026-114938 on November 17. Its November Critical Security Patch Update addresses 655 security vulnerabilities across the company’s product portfolio.
Oracle recommends that customers apply available security updates as soon as possible.
Organizations that cannot immediately update their Java implementation can temporarily disable the vulnerable hardware-accelerated Base64 feature by starting OpenJDK with:
-XX:-UseBASE64Intrinsics
Administrators running Java on x86-64 systems can alternatively disable AVX-512 instructions with:
-XX:UseAVX=2
These are temporary mitigations. Developers and administrators should update their Java runtime to the latest available version.
Source: www.bleepingcomputer.com


