Java2Shell (CVE-2026-114938): Critical Java Vulnerability Exposes Enterprise Applications to Remote Code Execution

Cybersecurity | Vulnerability Research
Java2Shell (CVE-2026-114938): OpenJDK RCE Fix & Patch Guide

Tracked as CVE-2026-114938, and commonly known as Java4Shell or Java2Shell, the vulnerability carries a CVSS v4.0 score of 9.2 (Critical).

With Java powering enterprise applications, authentication services and critical infrastructure, organisations should immediately assess their exposure.

What Is Java2Shell?

Java2Shell is a memory-corruption vulnerability affecting OpenJDK's hardware-accelerated Base64 decoder within the Java Virtual Machine (JVM).

The vulnerability occurs when specially crafted Base64 input triggers incorrect memory handling in the AVX-512 optimised decoding routine.

On affected systems, malformed input can overwrite adjacent heap memory, potentially allowing attackers to execute arbitrary code.

Successful exploitation may result in:

  • Remote Code Execution: Execute malicious commands within the affected Java process.
  • Information Disclosure: Access sensitive application memory, credentials or authentication tokens.
  • Denial of Service: Crash JVM processes and disrupt application availability.

Researchers have demonstrated exploitation against Java-based products including Jenkins, Jira, Confluence, Keycloak and JFrog Artifactory.

Importantly, exploitation depends on the Java runtime, processor architecture and application exposure to untrusted Base64 input.

Which Java Versions Are Affected?

The vulnerability affects certain OpenJDK and Oracle Java distributions running on x86-64 processors supporting AVX-512 VBMI instructions.

Java Version Affected Versions Fixed Oracle Release
Java 17 17.0.6–17.0.21 17.0.21.1
Java 21 Vulnerable builds before fix 21.0.13.1
Java 25 Vulnerable builds before fix 25.0.5.1
Java 27 Vulnerable builds before fix 27.0.1.1

‍

Standard Java 8 and 11 builds and ARM64 environments are not affected by this specific flaw. Oracle's Java 8 Enterprise Performance Pack is an exception.

Other Java distributions require vendor-specific security updates.

How Can Organisations Protect Themselves?

For IT and Security Teams

  1. Identify Java runtimes across servers, containers and third-party applications.
  2. Verify affected Java versions and AVX-512 VBMI processor support.
  3. Upgrade to vendor-confirmed patched releases.
  4. Temporarily disable vulnerable Base64 intrinsics using -XX:-UseBASE64Intrinsics where patching is delayed.
  5. Review suspicious activity and rescan systems to confirm remediation.

For Business Leaders

  1. Request an immediate Java2Shell exposure assessment.
  2. Prioritise internet-facing and business-critical applications.
  3. Confirm remediation timelines with internal teams and vendors.
  4. Implement continuous vulnerability monitoring and validation.

How to Fix Java2Shell (CVE-2026-114938)

Organisations should immediately upgrade affected Java runtimes to prevent potential remote code execution (RCE) through the vulnerable OpenJDK Base64 decoder.

1. Identify Vulnerable Java Versions

Check the installed Java runtime:

java -version

Identify active Java processes:

ps aux | grep '[j]ava'

Review Java installations across application servers, containers, CI/CD pipelines and third-party products such as Jenkins, Jira and Keycloak.

2. Upgrade to Patched Java Versions

Oracle released the following security updates on 17 November 2026:

Java Version Fixed Version
Java 17 17.0.21.1
Java 21 21.0.13.1
Java 25 25.0.5.1
Java 27 27.0.1.1
Java 8 Enterprise Performance Pack 8u513


Download the latest patched runtime from Oracle Java Downloads or your OpenJDK distribution vendor.

3. Apply Temporary Mitigation if Patching Is Delayed

If an immediate upgrade is not possible, disable the vulnerable hardware-accelerated Base64 decoding routine by adding the following JVM startup parameter:

-XX:-UseBASE64Intrinsics

Example:

java -XX:-UseBASE64Intrinsics -jar application.jar

Alternatively, restrict JVM acceleration to AVX2:

java -XX:UseAVX=2 -jar application.jar

These workarounds prevent execution of the vulnerable AVX-512 code path on affected JVMs. They may affect performance and should not replace security patches.

Restart all affected Java applications after applying the mitigation.

4. Verify Successful Remediation

Confirm the updated Java runtime using java -version and verify that all running JVM processes use the patched installation.

Rebuild affected container images, restart services and conduct vulnerability assessments to confirm remediation.

Continuous Vulnerability Assessment with Blacklock

Emerging vulnerabilities such as Java2Shell demonstrate why continuous security testing is essential.

Blacklock combines automated vulnerability scanning, expert-led penetration testing and AI-assisted validation to help organisations identify security risks and verify remediation.

Our recent research covered HTTP2Shell: Brotli Remote Code Execution and PHP2Shell: Critical PHP Vulnerabilities.

Blacklock also provides free vulnerability detection tools:

Don't wait for your next penetration test to assess critical exposure.

Sign up now and explore Blacklock to strengthen your organisation's continuous security assurance.

Share this post
Wordpress Security
Malware Analysis
Tools & Techniques
Pentests
PTaaS
Cyber Security
Technology
Subscribe to Our Newsletter

Join our newsletter today and enhance your knowledge with valuable insights. It's quick, easy, and free!

Be a Team Player
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Latest blogs

Latest updates in cybersecurity services

View All
Blacklock Blog Image
Cybersecurity | Vulnerability Research
Cybersecurity | Vulnerability Research
Cybersecurity | Vulnerability Research
Cybersecurity | Vulnerability Research
Cybersecurity | Vulnerability Research
Cybersecurity | Vulnerability Research