Java4Shell (CVE-2026-114938) fix: Update to these patched Java versions

19 Nov 2026

On November 17, 2026, security researchers at Calif disclosed a critical security vulnerability in OpenJDK (Open Java Development Kit) that could allow remote attackers to cause memory corruption, sensitive memory disclosure, or remote code execution.

 

With this blog, we will understand what Java4Shell is about, the threat it poses, and what organizations should do.

About Java4Shell (CVE-2026-114938)

Name/ Severity 

 

Affected component 

Vulnerability type 

Affected versions and platforms 

Fixed versions 

Other affected OpenJDK distributions 

Java4Shell/9.2 

OpenJDK HotSpot JVM – hardware accelerated Base64 decoder. 

Heap-based buffer overflow/memory corruption 

OpenJDK / Java 17: 17.0.6 through 17.0.21 

 

OpenJDK / Java 21: 21.0.13 and earlier affected builds 

 

OpenJDK / Java 25: 25.0.5 and earlier affected builds 
 
OpenJDK / Java 27: 27.0.1 and earlier affected builds 

Oracle Java SE 8: 8u511b33-perf (Performance Pack only) 

 

Oracle GraalVM for JDK: Affected releases of JDK 17 and 21 

 

Oracle GraalVM Enterprise Edition: 21.3.20.0.3 

OpenJDK / Java 17: 17.0.21.1 and later  

 

OpenJDK / Java 21: 21.0.13.1 and later 

 

OpenJDK / Java 25: 25.0.5.1 and later 
 

OpenJDK / Java 27: 27.0.1.1 and later 
 

Oracle Java SE 8: 8u513-perf (Performance Pack) 
 

Oracle GraalVM for JDK 17: 17.0.21.1 

 

Oracle GraalVM for JDK 21: 21.0.13.1 

 

Oracle GraalVM Enterprise Edition: 21.3.20.1 

The vulnerability also affects OpenJDK-based distributions, including: 
– Amazon Corretto 
– Azul Zulu 
– Eclipse Temurin 
– Microsoft Build of OpenJDK 
– Red Hat build of OpenJDK 
– SAP SapMachine 
– BellSoft Liberica 

 

Imagine a building has a flaw in its visitor handling system that allows someone to trick the system into not performing a security check when they go to a restricted area.

 

Java4Shell works in the same way.

 

The vulnerability affects OpenJDK’s Base64 decoder. Base65 decoder is a component that converts encoded data into its original form. However, under specific conditions, Base64 input can cause the decoder to write beyond the allocated heap buffer.

 

An attacker uses this loophole and specially crafted Base64 input that confuses the machine’s size calculation and writes data beyond its allocated storage compartment, overwriting the neighboring memory. This memory corruption causes the Java application to crash or allow the attacker to execute malicious code.

 

Calif’s researchers have demonstrated pre-authentication remote code execution against several widely used Java-based enterprise applications, including Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate.

 

Both Oracle and the OpenJDK project have released security fixes.

What attackers can do with Java4Shell?

Successful exploitation could have serious consequences for organizations running vulnerable Java-based services, including:

 

  • Remote Code Execution: Attackers could execute arbitrary code with the privileges of the affected Java process.
  • Application Compromise: Vulnerable enterprise applications, including authentication and development platforms, could be compromised.
  • Sensitive Information Exposure: Memory corruption may be leveraged to disclose data residing in the Java process’s memory.
  • Service Disruption: Malformed input could trigger JVM crashes, potentially affecting application availability.
  • Further Network Compromise: If an affected application is compromised, attackers may attempt additional activities based on the permissions and network access available to the compromised process.

What makes Java4Shell particularly dangerous?

Three things make Java4Shell particularly dangerous. It can allow attackers to:

 

  • Make an exploitation attempt without needing to log in or have valid credentials.
  • Execute commands remotely with the privileges of the Java process.
  • Potentially target other Java-based applications and services.

SharkStriker’s recommendations

  • Identify Java Deployments:** Inventory Java runtimes across servers, virtual machines, containers, cloud workloads, and enterprise applications. Include runtimes bundled within third-party products.
  • Verify Runtime and CPU Exposure: Check the exact Java vendor and build version, along with whether the underlying x86-64 processor supports the required AVX-512 capabilities.
  • Prioritize Critical Services: Give priority to internet-facing Java applications and authentication services, including Jenkins, Jira, Confluence, Keycloak, Artifactory, and PingFederate deployments.
  • Apply Vendor Security Updates: Upgrade affected Java runtimes to the latest fixed release provided by Oracle, OpenJDK, or the respective distribution vendor. For applications with bundled Java runtimes, follow the application vendor’s supported update process.
  • Restart Affected Services: Ensure Java processes are restarted after patching so that they load the corrected runtime. Rebuild and redeploy container images where necessary.
  • Apply Temporary Mitigations Where Required: If immediate patching is not possible, consider disabling the vulnerable Base64 intrinsic using the JVM option -XX:-UseBASE64Intrinsics. Alternatively, on affected x86-64 systems, -XX:UseAVX=2 can disable AVX-512 functionality. Validate compatibility and performance impact before deployment. These are temporary measures and do not replace patching.
  • Strengthen Monitoring: Monitor Java application processes, authentication endpoints, application errors, unexpected process execution, and outbound connections for suspicious activity.
  • Validate Remediation: After updates, verify the installed runtime version and confirm that all affected services and container workloads are running the patched build.

Get in Touch With us

We have explored what risk tolerance and risk appetite are and how important they are together in helping businesses align cybersecurity with their business goals. It can help CISOs, and C-suite make informed investment decisions for cybersecurity.

LEARN MORE