Vulnerabilities

CVE-2026-114938 Java4Shell Vulnerability Enables RCE in OpenJDK Across Jenkins, Jira, Confluence

November 18, 2026 00:00 · 7 min read
CVE-2026-114938 Java4Shell Vulnerability Enables RCE in OpenJDK Across Jenkins, Jira, Confluence

Critical OpenJDK Flaw Exposes Enterprise Java Applications to Remote Code Execution

A severe vulnerability identified as CVE-2026-114938 and nicknamed Java4Shell has been discovered in OpenJDK, the open-source implementation of the Java platform. The flaw resides in Java's hardware-accelerated Base64 decoding functionality and can be exploited by unauthenticated attackers to achieve remote code execution (RCE) on widely deployed enterprise applications. Security researchers at Calif disclosed the vulnerability on Tuesday, November 17, 2026, rating it critical with a CVSS 4.0 score of 9.2. Oracle assigned a lower severity rating of 8.1 (High) using the CVSS 3.1 scoring system.

Technical Root Cause: Memory Corruption in AVX-512 Base64 Decoder

The vulnerability stems from a bug in Java's Base64 decoder that leverages hardware acceleration on x86-64 processors supporting AVX-512 VBMI instructions. When processing specially crafted Base64 input, the decoder can overwrite portions of Java's memory, leading to information disclosure or arbitrary code execution. According to Calif, the memory corruption can be triggered with a minimal payload of 64 "A" characters followed by a single equals sign (AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=) on OpenJDK 17.0.6 and later. Older OpenJDK 17 versions require 128 "A" characters followed by the equals sign.

Base64 encoding is ubiquitous in authentication mechanisms, file uploads, and network communications, making the attack surface extensive. However, the flaw only manifests when the vulnerable hardware-accelerated decoding path is active, which depends on the underlying processor supporting AVX-512 capabilities.

Affected Java Distributions and Versions

Java4Shell impacts OpenJDK 17.0.6 and later, along with all downstream distributions built from the affected codebase. This includes:

Given Java's pervasive role in enterprise infrastructure — powering financial systems, web services, and critical business applications — the potential blast radius is substantial.

Exploitable Enterprise Applications: Unauthenticated and Authenticated RCE

Calif researchers demonstrated successful exploitation against a range of popular Java applications running default configurations. The affected applications fall into two categories based on authentication requirements:

Unauthenticated Remote Code Execution

Attackers can achieve RCE without any credentials against:

Authenticated Remote Code Execution

Valid credentials are required to exploit:

Additionally, the researchers confirmed exploitability in sample applications built on the Apache Struts and Spring Boot frameworks.

No Universal Exploit; Application-Specific Delivery Required

Calif emphasized that Java4Shell does not have a universal exploit. Attackers must identify an application-specific vector to deliver malicious Base64 data to the vulnerable decoder. The hardware dependency on AVX-512 VBMI support further constrains the conditions for successful exploitation.

AI-Assisted Discovery and Exploit Development

Researcher Quang Luong discovered the flaw using OpenAI's Codex AI coding assistant during an audit of OpenJDK internals. According to Calif, Luong identified the vulnerability in approximately one hour and developed an initial working exploit in two additional hours, at a total AI usage cost of less than $200. The company also reported that AI agents assisted in developing application-specific exploitation chains for the affected enterprise software.

Calif has published a proof-of-concept demonstrating the memory corruption but has not released weaponized exploits targeting the enterprise applications.

Patches and Mitigations

Oracle released patches for CVE-2026-114938 on November 17, 2026, as part of its November Critical Security Patch Update, which addresses 655 security vulnerabilities across its product portfolio. Oracle strongly recommends that customers apply the available security patches immediately.

Temporary Workarounds

For organizations unable to update immediately, Calif recommends the following JVM launch options to disable the vulnerable functionality:

These mitigations are temporary; all developers and administrators should prioritize updating Java runtimes to the latest patched versions.

Given the widespread deployment of affected Java versions and the critical nature of the impacted applications, security teams should assess their exposure immediately and apply patches or mitigations without delay.


Source: BleepingComputer

Source: BleepingComputer

Powered by ZeroBot

Protect your website from bots, scrapers, and automated threats.

Try ZeroBot Free