On November 17, 2026, Oracle released patches for CVE-2026-114938, a heap-based buffer overflow (CWE-122) in the hardware-accelerated Base64 decoder used by OpenJDK and its downstream distributions, such as Oracle Java SE, and Oracle GraalVM. The vulnerability, dubbed “Java4Shell” by finders Calif, can allow an unauthenticated remote attacker to crash a Java application or execute code with the privileges of its Java process. Oracle rates the vulnerability High, with a CVSS v3.1 score of 8.1 and high attack complexity, in its November security advisory.
Affected OpenJDK runtimes enable the vulnerable Base64 optimization by default when the Java virtual machine (JVM) can use the required x86-64 CPU features, including AVX-512 VBMI. A Java application exposes the flaw when it passes untrusted data to that optimized decoder. For example, a web service may decode HTTP Basic credentials before it checks the username and password. Red Hat reports no known exposure on ARM64 or on x86-64 processors without AVX-512 VBMI in its OpenJDK bulletin.
Calif’s disclosure states that they demonstrated unauthenticated remote code execution against several popular Java based applications, and they have published a local proof of concept (PoC) for CVE-2026-114938, which can test if a local JDK is vulnerable.
Given the ubiquitous nature of Java and its deployment across enterprise environments, Rapid7 recommends identifying and remediating affected systems, with a focus on Internet exposed systems, on an emergency basis and outside of normal patching cycles.
Rapid7 is actively monitoring the situation and will update this blog as new information arrives.
For the latest vendor release information, refer to Oracle's November security update notice and OpenJDK's vulnerability advisories.
Technical overview
CVE-2026-114938 affects a hardware-specific optimization in HotSpot, the Java virtual machine used by many OpenJDK distributions. When frequently used Base64 decoding code is compiled, HotSpot can substitute a native routine that processes multiple bytes at once. The vulnerable path requires an x86-64 runtime, CPU features including AVX-512 VBMI, and effective JVM settings that permit the optimizing compiler and Base64 intrinsic. Consequently, an affected Java version alone does not establish that a particular application is exploitable.
The defect occurs when that routine processes a malformed final Base64 group. Its calculation of the remaining output length can become negative, enabling a wider memory write than the destination can accommodate. Confirmed malformed-tail cases produce a 64-byte store extending 62 or 63 bytes beyond the calculated decoded-output length. Java subsequently rejects the malformed input, but catching that exception does not undo the corruption. Damage to another object can remain unnoticed until later activity, including garbage collection, crashes the JVM.
Turning this constrained overwrite into code execution requires additional work. A reliable exploit typically needs to influence which objects occupy the affected memory, convert the initial corruption into useful access to other objects, and identify application or runtime behavior that permits further execution. The practical outcome therefore depends on the application, JVM build, memory layout, and security boundaries. This distinction explains why a working corruption trigger does not establish a portable exploit for every Java service.
Remote exposure arises when an application passes attacker-controlled data to the affected decoder. Authentication headers and tokens are relevant examples, but reachability must be established for the actual implementation. The published OpenJDK fix hands final groups shorter than four bytes to the ordinary Java decoder. Organizations should apply their runtime vendor's fixed build and restart affected JVMs; disabling Base64 intrinsics with -XX:-UseBASE64Intrinsics is a temporary mitigation where supported.
Mitigation guidance
Rapid7 recommends applying the November security update as soon as possible, starting with internet-facing services that decode credentials or tokens before authentication. Identify the runtime vendor and full build each service uses, including Java runtimes bundled with applications, appliances, and container images.
OpenJDK lists release versions 17, 21, 25, and 27 as affected by CVE-2026-114938 in its November 17 advisory. Red Hat identifies OpenJDK 17.0.6 as the earliest affected version 17.
Oracle separately identifies its Java 8 Enterprise Performance Pack as affected in the Java risk matrix. The table below pairs affected Oracle builds with the November updates listed in the JDK security baselines, Enterprise Performance Pack release notes, and GraalVM release calendar.
Product Name
Vulnerable Java Version
Patched Version (Official Release Notes)
Oracle Java SE 8 Performance Edition
8u511b33-perf
Oracle Java SE 17
17.0.21.0.3
Oracle Java SE 21
21.0.13.0.3
Oracle Java
[…]
Content was trimmed to protect the source. Please visit the original article for the full text.
Read the original article:
CVE-2026-114938: Reported Critical Pre-authentication Remote Code Execution in Java 17
