Java4Shell (CVE-2026-114938): Critical Java Vulnerability Requires Specific Conditions to Exploit

Java4Shell (CVE-2026-114938): Critical Java Vulnerability Requires Specific Conditions to Exploit

A newly disclosed Java vulnerability, nicknamed Java4Shell, could allow attackers to execute code remotely without authentication. Security researchers have demonstrated exploitation paths involving widely used applications such as Keycloak, Jenkins, Jira, and Confluence, making this a significant concern for enterprise environments.

Tracked as CVE-2026-114938, the vulnerability affects Java's hardware-accelerated Base64 decoder. However, exploitation is not straightforward: specific Java versions, processor capabilities, and application behaviour must align.

For vulnerability details and ongoing intelligence, see the BaseFortify CVE-2026-114938 report.

What Makes Java4Shell Dangerous?

Java4Shell is a heap-based buffer overflow (CWE-122) in the Java runtime's optimized Base64 decoder.

Base64 decoding is commonly used to process authentication credentials, tokens, and encoded application data. Under certain conditions, maliciously crafted input can trigger memory corruption, potentially resulting in application crashes, information disclosure, or remote code execution (RCE).

Oracle assigns the vulnerability a CVSS 3.1 score of 8.1 (High), reflecting its significant impact but relatively high attack complexity.

Crucially, the vulnerability requires an affected x86-64 processor supporting AVX-512 VBMI instructions. ARM64 systems and older x86-64 processors without these instructions are not known to be affected.

Affected Java Versions

The European Union Vulnerability Database (EUVD) identifies the following affected Oracle products and versions:

Product Affected version
Oracle Java SE 8u511b33-perf
Oracle Java SE 17.0.21.0.3
Oracle Java SE 21.0.13.0.3
Oracle Java SE 25.0.5.0.3
Oracle Java SE 27.0.1.0.3
Oracle GraalVM for JDK 17.0.21.0.3
Oracle GraalVM for JDK 21.0.13.0.3
Oracle GraalVM Enterprise Edition 21.3.20.0.3

These entries identify affected releases, not necessarily the complete range of vulnerable versions. Earlier affected builds and Java distributions including Eclipse Temurin, Amazon Corretto, and Azul Zulu must also be considered.

See ENISA's EUVD-2026-127648 entry.

Why Exploitation Requires Additional Steps

Despite the potential for unauthenticated remote code execution, Java4Shell is not a universal exploit against every Java application.

An attacker needs several conditions to align:

  1. Vulnerable runtime: The target must execute an affected Java build.
  2. Compatible hardware: The processor must support the vulnerable AVX-512 instruction path.
  3. Reachable Base64 decoding: Attacker-controlled input must reach the affected decoder.
  4. Successful memory exploitation: The attacker must manipulate the resulting memory corruption to achieve a useful outcome, potentially requiring application-specific techniques.

The last requirement is particularly important. Triggering a buffer overflow is not equivalent to obtaining remote code execution. Reliable exploitation can require knowledge of the application's memory behaviour and additional preparation.

Nevertheless, researchers have demonstrated working exploitation techniques, so the difficulty should not be interpreted as an absence of risk.

Applications That May Be Exposed

Researchers have reported pre-authentication exploitation against several popular Java-based products:

  • Keycloak — Identity and access management
  • Jenkins — Continuous integration and automation
  • Atlassian Jira and Confluence — Project management and collaboration
  • JFrog Artifactory — Artifact repository management
  • PingFederate — Enterprise authentication and federation

Other Java applications may also be exposed if they process attacker-controlled Base64 data through a vulnerable runtime.

These products are not necessarily vulnerable in every deployment. The actual risk depends on the bundled or installed Java version, processor architecture, and accessible application functionality.

How to Check and Patch Your Systems

Administrators should prioritize internet-facing Java applications, particularly authentication and identity-management services.

1. Identify the Java runtime

On Linux, check the active Java version:

java -version

Remember that applications and Docker containers may bundle their own Java runtime rather than use the system installation.

2. Check processor compatibility

On Linux, check whether AVX-512 VBMI is exposed:

grep -m1 -o 'avx512vbmi' /proc/cpuinfo

If the command returns avx512vbmi, the processor meets an important hardware prerequisite. This does not establish that the installed Java runtime or application is vulnerable.

3. Install patched Java releases

Oracle has published fixed releases for affected Java SE versions:

Java version Fixed Oracle release
Java 8 Performance Pack 8u513-perf
Java 17 17.0.21.1
Java 21 21.0.13.1
Java 25 25.0.5.1
Java 27 27.0.1.1

For other Java distributions, use the corresponding security release provided by the vendor.

On Ubuntu or Debian systems using distribution-managed OpenJDK packages, administrators can check for available updates with:

sudo apt update
apt list --upgradable | grep -i openjdk

Install the appropriate updated OpenJDK packages once the distribution has published a fix. Restart affected applications afterward and verify the runtime version they are actually using.

4. Apply temporary mitigations when patching is not immediately possible

Red Hat recommends disabling the vulnerable optimized Base64 implementation using this JVM startup option:

-XX:-UseBASE64Intrinsics

Alternatively, on x86-64 systems:

-XX:UseAVX=2

The second option disables AVX-512 more broadly and may affect performance. Neither option should be applied blindly to unsupported runtimes or architectures.

For applications with bundled Java runtimes, follow the software vendor's patching and mitigation guidance.

Important: Java4Shell is a serious vulnerability, but a vulnerable Java version alone does not guarantee exploitability. Hardware capabilities, application behaviour, and additional exploitation steps all matter. Organizations should prioritize patching while assessing their actual exposure rather than assuming every Java deployment is immediately exploitable.

Is Java4Shell Being Actively Exploited?

As of 18 November 2026, there is no confirmed evidence of widespread malicious exploitation in the wild.

However, proof-of-concept techniques have been demonstrated, and further research could make exploitation more accessible.

The absence of confirmed attacks is not a reason to delay patching. Organizations should assess their exposure and apply fixes according to the risk presented by each deployment.

Track Java4Shell with BaseFortify

BaseFortify helps organizations identify vulnerabilities affecting their infrastructure by tracking the software components they use.

For example, an organization running Oracle Java SE 17 can register the relevant product CPE, such as:

cpe:2.3:a:oracle:jre:17.0.21.0.3:*:*:*:*:*:*:*

The exact CPE should be verified against the installed product and version.

Once the component is registered and matched against vulnerability intelligence, BaseFortify can identify associated threats, including CVE-2026-114938, as the corresponding CPE data becomes available.

More importantly, the component remains monitored for future vulnerabilities, helping administrators identify new security issues affecting their Java installations without repeatedly searching vulnerability databases.

For technical details, severity assessments, and updates, visit the BaseFortify Java4Shell vulnerability report.

Register for free at BaseFortify.

References