HudHud Tech — Tech & AI news platform
Wednesday, 18 November 2026
Breaking
Cybersecurity

Java4Shell Vulnerability Exposes Major Java Applications to RCE Attacks

18 November 2026 3 min read هدهد تك | Hudhud Tech

A critical vulnerability known as Java4Shell in OpenJDK, the open-source implementation of Java, enables unauthenticated attackers to remotely execute code on widely used enterprise applications, including Jenkins, Atlassian Jira, Confluence, and Keycloak.

Java is a predominant programming platform globally, supporting enterprise applications, web services, financial systems, and essential business infrastructure. Vulnerabilities in its core components can impact a diverse range of applications due to the shared Java runtime.

The vulnerability, tracked as CVE-2026-114938, is a memory-corruption flaw in Java’s hardware-accelerated Base64 decoding functionality. This flaw can be exploited to disclose sensitive information from memory or achieve remote code execution (RCE).

Security researchers at Calif disclosed the flaw on November 17, rating it critical with a CVSS score of 9.2. In contrast, Oracle assigned a lower severity rating of 8.1 (High) using CVSS 3.1.

Java4Shell affects OpenJDK 17.0.6 and later versions, as well as Java distributions built from the affected code, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, and Red Hat OpenJDK.

The vulnerability arises from a bug in Java’s Base64 decoder, which processes encoded data commonly found in authentication, file uploads, and network communications. According to Calif, specially crafted Base64 data can cause the decoder to overwrite portions of Java’s memory, potentially allowing attackers to steal sensitive information or execute malicious code.

The researchers demonstrated that the memory corruption can be triggered with just 64 “A” characters followed by a single equals sign (=):

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=

Older OpenJDK 17 versions require 128 “A” characters followed by the equals sign. The flaw specifically affects a hardware-accelerated decoding function utilized on certain x86-64 processors that support AVX-512 instructions.

Researchers successfully exploited this bug to perform remote code execution against various widely used Java applications running with their default configurations, including:

  • Unauthenticated RCE: Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate.
  • Authenticated RCE: Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker.

Calif also exploited the flaw in sample applications built using the Apache Struts and Spring Boot frameworks. However, the researchers noted that Java4Shell does not have a universal exploit; attackers must find application-dependent methods to deliver malicious Base64 data to the vulnerable decoder for code execution.

The vulnerability requires the affected hardware-accelerated AVX-512 decoding function, which depends on supported x86-64 processors with AVX-512 VBMI capabilities. Calif stated that researcher Quang Luong discovered the flaw using OpenAI’s Codex AI coding assistant during an audit of OpenJDK’s internals.

Luong identified the flaw in about one hour and developed an initial working exploit in an additional two hours, incurring an AI usage cost of less than $200. The company reported that AI agents also assisted in developing additional application-specific exploitation chains.

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

Oracle released patches for CVE-2026-114938 on November 17 as part of its November Critical Security Patch Update, addressing 655 security vulnerabilities across its product portfolio. The company urges customers to apply the available security patches promptly.

For those unable to update their Java implementations immediately, Calif recommends disabling the vulnerable hardware-accelerated Base64 functionality by launching OpenJDK with the -XX:-UseBASE64Intrinsics option. Alternatively, administrators running Java on x86-64 systems can use -XX:UseAVX=2 to disable AVX-512 instructions. However, these workarounds are temporary mitigations, and all developers should update their Java runtimes to the latest version.

 

Source: BleepingComputer

What do you think of this story?

Share this story: