Java4Shell (CVE-2026-114938): When Base64 Decoding Leads to RCE
On November 17, 2026, security researchers at Calif published Java4Shell (CVE-2026-114938), a vulnerability in OpenJDK’s optimized Base64 decoder. Under the right conditions, malformed input can corrupt memory and allow an attacker to execute code in a Java application, potentially before authentication.
Base64 decoding is an everyday operation, used to handle credentials, tokens, and messages. That makes a flaw in the runtime worth investigating even when your own application code has not changed.
The important question is which Java build your application actually uses, on which processor, and whether untrusted data reaches the affected decoder. Here is how those pieces fit together, and what to do next.
Last reviewed: November 18, 2026. Vendor builds and exploitation reports may change after publication.
Java4Shell at a glance
| Item | Details |
|---|---|
| CVE identifier | CVE-2026-114938 |
| Affected component | OpenJDK HotSpot’s accelerated java.util.Base64 decoding path |
| Vulnerability | Heap-based buffer overflow, classified as CWE-122 |
| Potential impact | Memory disclosure, JVM crashes, and remote code execution |
| Runtime scope | Unpatched OpenJDK builds containing the optimization, reported from 17.0.6 onward, including the 21, 25, and 27 lines; some Oracle performance builds are also affected |
| Hardware requirement | x86-64 with the required AVX-512 VBMI features, with the affected intrinsic enabled |
| Severity | Oracle: 8.1 High, CVSS v3.1; Calif: 9.2 Critical, CVSS v4.0 |
| Remediation | Install your Java vendor’s fixed build and restart the application |
Oracle’s November security advisory provides the vendor assessment. The scores use different CVSS versions and should not be presented as interchangeable ratings.
How a Java optimization became a memory-safety problem
Java normally checks array boundaries for developers. But the runtime also uses native routines to accelerate common operations, and those routines need to enforce their own limits.
In this case, malformed Base64 padding can make an optimized routine calculate an invalid output length and write beyond its destination array. Calif describes a case where 62 bytes are written out of bounds. The Java layer eventually rejects the input, but the memory corruption has already happened.
Calif attributes the discovery and technical research to Quang Luong, with exploit improvements by Jenish Rakholiya. Oracle also credits Luong and Albert Yang for this CVE. The Calif disclosure includes the technical explanation and demonstrations; it is the original research publication behind the Java4Shell name.
The upstream code change adds a guard that sends short trailing fragments back to Java handling instead of processing them in the affected optimized path.
Does this expose every Java application?
No. Exposure depends on the runtime, CPU, JVM options, and application together.
The vulnerable path uses x86-64 instructions unavailable on ARM64. It also requires particular CPU features: avx512f, avx512bw, avx512vbmi, and bmi2. A vulnerable build on a processor without those features does not execute this path.
The application must also pass attacker-controlled data to the affected decoder. Authentication flows are an obvious place to investigate, but file processing, messaging, and client connections can matter too. A service does not have to expose a feature called “Base64 decoding” for the runtime to use it internally.
Calif reports pre-authentication RCE demonstrations against products including Jira, Confluence, Jenkins, and Keycloak. Those results describe tested deployments, not every installation of those products.
VulnCheck independently reproduced the flaw and distinguishes relatively straightforward crashes from code execution, which requires more involved, application-specific exploitation. A short corruption trigger is not a universal server-takeover payload.
Which versions should you check?
The widely reported starting point is OpenJDK 17.0.6, but “Java 17 or newer” is too broad to use as a final verdict. Fixed builds are now available, and vendors use different release numbers.
There is also a Java 8 exception worth keeping in view: Oracle lists 8u511b33-perf, its Enterprise Performance Pack build, as affected. This does not mean all Java 8 installations are vulnerable. Red Hat identifies its OpenJDK 8 and 11 builds as unaffected in its product bulletin.
CERT-EU’s advisory lists the following fixed releases. Oracle’s linked release notes confirm the corresponding JDK updates:
| Runtime line | Fixed Oracle release |
|---|---|
| Java 17 | 17.0.21.1 |
| Java 21 | 21.0.13.1 |
| Java 25 | 25.0.5.1 |
| Java 27 | 27.0.1.1 |
These are Oracle release numbers, not a universal patch matrix for Temurin, Corretto, Zulu, or other distributions. GraalVM and Java 8 performance builds also need their own vendor-specific update check.
Check the runtime your application actually uses
Start with the Java executable configured for the service, rather than whichever java happens to be in your shell’s path:
/path/to/application/java -version
Record the vendor and full build number. Check bundled runtimes inside product directories, containers, and appliances too: updating the host’s Java package may leave those copies untouched.
On Linux, inspect the CPU features visible to the application environment:
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' |
grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
All four flags are relevant. Their presence establishes a hardware prerequisite, not proof that the application is exploitable. Review the service’s JVM startup options and its handling of untrusted input alongside the vendor’s package status.
Patch the runtime, or temporarily disable the optimization
Install a build explicitly fixed for this CVE from your Java or application vendor, then restart the affected JVMs. For containers, rebuild the image and replace running instances. Where a product bundles Java, follow its supported update procedure.
If patching needs more time, CERT-EU recommends disabling the Base64 intrinsic at JVM startup:
-XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics
An alternative for x86-64 only is:
-XX:UseAVX=2
That second option disables AVX-512 more broadly and may affect performance. Do not apply it indiscriminately to mixed-architecture deployments: it can prevent an ARM JVM from starting.
Both approaches require a restart. Confirm that the options reached the application process and test normal behavior. Running a separate java command with the flag only changes that new invocation; it does not mitigate an existing service.
The Canadian Cyber Centre’s alert also recommends inventorying bundled Java environments and prioritizing exposed applications. The workaround buys time; the vendor fix remains the permanent response.
Follow Java vulnerabilities with OpenCVE
Java4Shell is a reminder that an application’s security depends on the runtime underneath it as well as its own dependencies. Following updates to both helps your team understand what needs attention as new information arrives.
OpenCVE lets you monitor vendors and products, receive CVE updates through automations, and assign vulnerabilities to the people responsible for reviewing them.