ThreatIntelligence-IncidentResponse

Java4Shell (CVE-2026-114938): OpenJDK RCE Vulnerability FAQ


Java4Shell is a flaw in how Java decodes Base64 data. Calif, which found it, says it can let attackers run code on widely used Java applications without logging in. Oracle released fixed Java builds on November 17, and Calif is withholding its exploits for individual applications for now.

Key takeaways

  1. CVE-2026-114938, dubbed Java4Shell, is an OpenJDK memory corruption vulnerability that Oracle scores 8.1 on CVSS 3.1, and Calif says its testing showed attackers could run code without logging in on applications such as Atlassian Jira and Jenkins.
  2. As of November 17, Tenable is not aware of any reports that attackers have exploited this flaw, though Calif has published a PoC that triggers the bug without taking control of the system and a second researcher reports building a working exploit.
  3. Oracle released fixed builds on November 17, and according to Calif, only systems running an affected Java version on x86-64 processors that support AVX-512 VBMI can be affected.

Background

Tenable’s Research Special Operations (RSO) team has compiled this blog to answer Frequently Asked Questions (FAQ) regarding Java4Shell, a vulnerability in OpenJDK that was patched on November 17, 2026.

FAQ

When was Java4Shell first disclosed?

On November 17, security firm Calif said on X that it had found and reported the flaw, and that details of Java4Shell, as Calif named it, had leaked ahead of a fix. Later that day, Oracle released its November 2026 Critical Security Patch Update (CSPU), and the OpenJDK Vulnerability Group published its own advisory. Calif then published its technical write-up. Oracle credits Quang Luong of Calif.io and Albert Yang for reporting the vulnerability.

What is CVE-2026-114938?

CVEDescriptionCVSSv3.1
CVE-2026-114938OpenJDK Base64 Decoder Memory Corruption Vulnerability (Java4Shell)8.1

CVE-2026-114938 is a memory corruption vulnerability in the part of Java that decodes Base64, a common format that applications use to send data such as login details and file uploads. Oracle assigned it a CVSS 3.1 score of 8.1 and rates its attack complexity as high. Calif says it scores 9.2 under CVSS 4.0. An attacker does not need to log in to exploit it remotely. According to Oracle, the flaw can only be exploited when an application passes untrusted data to the affected Java APIs, such as through a web service.

Is CVE-2026-114938 among the Java fixes in Oracle’s November 2026 CSPU?

Yes. CVE-2026-114938 is addressed by one of the 11 Java SE security patches in Oracle’s November 2026 CSPU, released November 17. For a breakdown of all the patches in this release, see our blog post on Oracle’s November 2026 CSPU.

What is known about CVE-2026-114938?

The flaw is in a performance shortcut that Java uses to decode Base64 data faster on certain Intel and AMD processors. When the shortcut receives a specially crafted Base64 string, it writes data beyond the memory it set aside. That can corrupt other information the application is holding in memory.

According to Calif, an attacker can use this flaw in two ways. The first, which Calif calls “JavaBleed,” lets an attacker read the application’s memory. That memory may hold secrets such as keys and tokens. The second lets an attacker run their own code on the server. Calif also says that each application needs its own exploit, and that a failed attempt can crash the application, though an attacker can often try again.

Exposure depends on the processor as well as the Java version. According to Calif, Java uses the affected code only on x86-64 processors that support a feature called AVX-512 VBMI. These include Intel Xeon processors from the Granite Rapids, Emerald Rapids, Sapphire Rapids and Ice Lake families, as well as AMD processors based on Zen 4 or newer. Calif says systems with ARM64 processors are not affected. On Linux, a system meets this requirement when its processor reports all four of the avx512f, avx512bw, avx512vbmi and bmi2 flags.

Which versions of Java are affected?

The OpenJDK Vulnerability Group lists the Java 17, 21, 25 and 27 release lines as affected by CVE-2026-114938. Calif says OpenJDK 17.0.6 and newer are affected. Oracle lists the following Oracle builds as affected:

ProductAffected versions (and likely earlier)
Oracle Java SE8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3
Oracle GraalVM for JDK17.0.21.0.3, 21.0.13.0.3
Oracle GraalVM Enterprise Edition21.3.20.0.3

Oracle lists only builds it supports and says earlier versions are likely also affected. The Java 8 build on Oracle’s list is its Enterprise Performance Pack. The OpenJDK advisory does not list standard Java 8 or Java 11 as affected by this vulnerability.

I don’t use Oracle’s Java builds. Am I affected?

Possibly. The flaw is in OpenJDK code, and according to Calif, the following Java distributions built from OpenJDK are also vulnerable:

  • Amazon Corretto
  • Eclipse Temurin
  • Microsoft Build of OpenJDK
  • Azul Zulu
  • BellSoft Liberica
  • SAP SapMachine
  • Red Hat OpenJDK
  • Oracle OpenJDK

Each vendor releases fixed builds on its own schedule, so check with your distribution’s vendor for its fixed versions.

Which applications are known to be affected?

Calif says its initial testing showed that an attacker could run their own code on the following applications in their default configurations, when they run on an affected version of Java on a processor that supports AVX-512 VBMI. The list is not exhaustive, according to Calif.

ApplicationCalif’s result
KeycloakExploitable before login
Atlassian JiraExploitable before login
Atlassian ConfluenceExploitable before login
JFrog ArtifactoryExploitable before login
JenkinsExploitable before login
PingFederateExploitable before login
Apache Kafka BrokerExploitable after login
Apache SolrExploitable after login
ElasticsearchExploitable after login
GerritExploitable after login
SpinnakerExploitable after login

Calif also said it ran its own code on sample applications built on frameworks including Apache Struts and Spring Boot. Calif adds that everyday functions, including authentication and file uploads, can lead to the vulnerable code, so more applications than the ones Calif tested may be exposed. Calif says researcher samczsun gave it a client-side exploit, and that a Java program can be compromised when it connects over TLS to a server an attacker controls, even if the program offers no service of its own. Calif says it will publish its exploits for individual products at a later date.

Has Java4Shell been exploited in the wild?

As of November 17, we are not aware of any reports of exploitation of CVE-2026-114938, and it is not listed in the Cybersecurity and Infrastructure Security Agency’s (CISA) Known Exploited Vulnerabilities (KEV) catalog.

Is there a proof-of-concept (PoC) available?

Yes. Calif published a PoC alongside its write-up that triggers the flaw without taking control of the system. It shows whether a given Java version and processor reproduce the bug. It does not show whether a particular application is exposed.

On November 17, Kevin Breen of Immersive said on X that they had developed a working exploit for CVE-2026-114938. According to Breen, the exploit has to be adapted to each application. It works only on a vulnerable version of Java running on a processor that supports AVX-512 VBMI, and only against applications that decode Base64 data. Breen also said that Apache Tomcat’s Basic authentication and the java-jwt library provide ways to exploit the flaw before a user logs in. The post does not say that the exploit has been released.

Are patches available?

Yes. On November 17, Oracle released the following fixed builds:

Java lineAffected Oracle buildFixed Oracle build
Java 8 Enterprise Performance Pack8u511b33-perf8u513-perf
Java 1717.0.21.0.317.0.21.1
Java 2121.0.13.0.321.0.13.1
Java 2525.0.5.0.325.0.5.1
Java 2727.0.1.0.327.0.1.1

For Oracle GraalVM, see Oracle’s advisory. For other Java distributions, see each vendor’s advisory.

Are there any mitigations?

Calif identified two Java startup options that keep the vulnerable code from running. The first, -XX:-UseBASE64Intrinsics, turns off the Base64 shortcut. The second, -XX:UseAVX=2, turns off AVX-512 instructions. According to Calif, the second option applies only to x86-64 systems, and Java on ARM processors fails to start with it. Neither Oracle nor the OpenJDK Vulnerability Group mentions these options in its advisory.

Has Java been targeted historically?

Yes. CISA’s KEV catalog includes 13 vulnerabilities in Oracle Java SE and the Java Runtime Environment (JRE), six of which are known to have been used in ransomware campaigns. Those six are:

CVEKEV nameAdded to KEV
CVE-2013-0431Oracle JRE Sandbox Bypass VulnerabilityMay 25, 2022
CVE-2013-0422Oracle JRE Remote Code Execution VulnerabilityMay 25, 2022
CVE-2013-2465Oracle Java SE Unspecified VulnerabilityMarch 28, 2022
CVE-2012-4681Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution VulnerabilityMarch 3, 2022
CVE-2012-1723Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution VulnerabilityMarch 3, 2022
CVE-2012-0507Oracle Java SE Runtime Environment (JRE) Arbitrary Code Execution VulnerabilityMarch 3, 2022

Has Tenable Research classified this vulnerability as part of Vulnerability Watch?

Yes. CVE-2026-114938 has been classified as a “Vulnerability of Interest” as part of Vulnerability Watch.

Are Tenable products affected by this vulnerability?

Tenable is aware of this vulnerability and is investigating whether it affects any Tenable products.

Has Tenable released any product coverage for this vulnerability?

A list of Tenable plugins for this vulnerability can be found on the individual CVE page for CVE-2026-114938 as they’re released. This link will display all available plugins for this vulnerability, including upcoming plugins in our Plugins Pipeline.

How can Tenable customers find affected assets?

Tenable One Vulnerability Management customers can go to Explore > Software to view installed software across their assets, then filter by product name and version to look for Java installations to compare against the affected versions above. Exposure also depends on the processor, as described above. Software data comes from credentialed and agent scans. For details, see Use the Software Page.

Tenable One Vulnerability Management customers can also use the Java Visibility and Exposures report, which lists Java installations and the hosts where they were detected.

Tenable One Attack Surface Management customers can find internet-facing assets running Java with the filter Programming Languages contains Java. Those assets can then be scanned with other Tenable sensors to check whether they are affected by CVE-2026-114938.

Get more information

Join Tenable’s Research Special Operations (RSO) Team on Tenable Connect for further discussions on the latest cyber threats.



Source link