Java4Shell: OpenJDK flaw could allow remote code execution

The CVE-2026-114938 vulnerability in the Java runtime affects hardware-accelerated Base64 decoding. Oracle has released fixes, and Red Hat has also published temporary mitigations.

Java4Shell OpenJDK flaw, designated CVE-2026-114938, could under certain conditions allow remote code execution without authentication. On November 17, Oracle included it in its Critical Security Patch Update for Oracle Java SE and GraalVM and rated it 8.1 out of 10 on the CVSS scale.

The problem is not located in one specific application, but in the Java runtime. It involves memory corruption in the hardware-accelerated path of the java.util.Base64.Decoder. To exploit it, an application must decode Base64 data that an attacker can influence.

The Java4Shell OpenJDK flaw is tied to specific hardware

According to Red Hat’s security bulletin, the issue affects OpenJDK 17.0.6 and later on x86-64 processors supporting the AVX-512 VBMI extension. ARM64 and x86-64 systems without AVX-512 VBMI are not currently known to be affected.

This condition is important when determining update priorities. The mere presence of a Java application is therefore not enough to confirm risk. The runtime version, processor used, JVM launch parameters, and whether the service processes Base64 inputs supplied by users or other untrusted sources should also be verified.

Researchers from Calif, who use the Java4Shell designation, reported demonstrations of pre-authentication remote code execution in the default configurations of several products, including Jenkins, Jira, Confluence, and Keycloak. However, this claim does not automatically apply to every deployment of these products or to every Java application.

Fixes are available, and a temporary mitigation also exists

Oracle included CVE-2026-114938 in its November security package for Oracle Java SE and GraalVM. Administrators should identify Java runtimes in production systems and monitor OpenJDK distributor errata as well as announcements from application vendors that provide their own or bundled JVM.

As a temporary measure before deploying a fix, Red Hat recommends disabling Base64 intrinsics with the following parameter:

-XX:-UseBASE64Intrinsics

On x86-64, Red Hat lists -XX:UseAVX=2 as an alternative. Both options are intended to mitigate the risk, not replace an update. Their deployment should account for the specific way the JVM is launched, such as container, system service, or application server settings.

Externally accessible Java services should be prioritized

Internet-accessible Java services running on affected x86-64 hardware deserve the highest attention, particularly authentication and enterprise applications that receive or process untrusted Base64 data. The Java runtime may be bundled directly in an application, container image, or device, so a standard review of application dependencies may not find all relevant installations.

On November 17, the Canadian Cyber Centre stated that it had no information about active exploitation of the vulnerability. Successful attacks in the wild have also not been publicly confirmed. Nevertheless, organizations should verify their deployments and apply available fixes or temporary mitigations where an update is not yet possible.

Further developments will depend mainly on the release of fixes for OpenJDK distributions and products with bundled JVMs, any publication of working exploits, and clarifications regarding affected versions or products.

Sources

Verified and updated: November 18, 2026 07:03

Sharing