Java4Shell (CVE-2026-114938) is a critical memory-corruption flaw in OpenJDK’s Base64 decoder, disclosed on November 17, 2026. On x86-64 servers whose CPUs support AVX-512 VBMI, a malicious Base64 string can crash the Java process and, in some applications, let an attacker run code without logging in. The fix is to update Java to a patched release.
Java runs a huge share of business software, from Jira and Jenkins to identity platforms and data systems, and Base64 decoding happens constantly inside it. That combination is why security teams are treating Java4Shell as a priority, even though it only affects specific hardware and is harder to exploit than its name suggests.
This guide explains what Java4Shell is in plain language, who is and isn’t affected, how to check your systems, and how to fix or mitigate it. Details may change as more vendors publish patches, so check your Java vendor’s advisory for the latest versions.
Java4Shell at a Glance
| Details | |
|---|---|
| CVE | CVE-2026-114938 |
| Name | Java4Shell |
| Component | OpenJDK’s hardware-accelerated Base64 decoder (java.util.Base64) |
| Severity | 9.2 Critical (CVSS 4.0, per Calif); 8.1 High (CVSS 3.1, per Oracle, which rates attack complexity as high) |
| Disclosed | November 17, 2026; Oracle released patched builds the same day, and other vendors are following |
| Discovered by | Quang Luong of the security research firm Calif |
| Affected Java | OpenJDK 17.0.6 and later, plus the 21, 25, and 27 release lines, across major vendors (Oracle, Eclipse Temurin, Amazon Corretto, Microsoft, Azul, Red Hat, and others) |
| Affected hardware | x86-64 CPUs with AVX-512 VBMI, such as Intel Xeon Ice Lake and newer, and AMD Zen 4 and newer |
| Not affected | ARM64 (including AWS Graviton and Apple silicon), x86-64 CPUs without AVX-512 VBMI, OpenJDK 17.0.0 through 17.0.5 |
| Impact | JVM crash (denial of service), memory disclosure, and remote code execution in some applications |
| Exploited in the wild? | No reports as of November 17, 2026; not in CISA’s Known Exploited Vulnerabilities catalog |
What Is Java4Shell?
Base64 is a way to turn binary data into plain text so it can travel safely through systems built for text. It’s everywhere: login tokens (JWTs), HTTP Basic authentication headers, email attachments, certificates, API payloads, and single sign-on messages all use it.
To make Base64 fast, OpenJDK’s just-in-time compiler swaps the normal Java decoding code for a hand-optimized routine, called an intrinsic, that uses advanced CPU instructions. On processors with AVX-512 VBMI, it uses 512-bit instructions to decode up to 64 bytes at a time.
Java4Shell is a bug in that optimized routine. When a short input ends with certain padding characters (= or ==), a length calculation goes below zero. The routine then writes a full 64-byte block instead of only the bytes it should, writing past the end of the output buffer and corrupting nearby memory in the Java heap.
In Java, memory corruption is rare because the language normally checks every array access. This bug happens inside the low-level optimized code, below those safety checks, which is what makes it serious.
Why the Name?
The name echoes Log4Shell, the 2021 Log4j flaw, and PHP2Shell, a critical flaw in PHP disclosed in October 2026. It signals a bug in a building block used by countless applications that can lead to a remote shell. See What Is a Zero-Day Vulnerability? for the Log4Shell story and WordPress Under Attack for PHP2Shell.
Why Java4Shell Matters
Many applications decode Base64 that comes straight from the internet, often before checking who the user is. An attacker who can get a crafted string to the decoder can at least crash the Java process. With careful preparation of the heap, Calif says it achieved remote code execution in the default configurations of widely used products:
- Without logging in: Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins, and PingFederate.
- After logging in: Apache Kafka, Apache Solr, Elasticsearch, Gerrit, and Spinnaker.
- Client side: a Java program that connects over TLS to a malicious server can also be compromised.
Calif has published a small proof of concept that only demonstrates the bug, and says it is withholding the product-specific exploits until organizations have had time to update.
How It Compares to Log4Shell
| Log4Shell (2021) | Java4Shell (2026) | |
|---|---|---|
| Where | Log4j logging library | The Java runtime itself (OpenJDK) |
| Hardware requirement | None | x86-64 with AVX-512 VBMI |
| Exploit difficulty | Very easy: one text string | Harder: needs heap grooming and a tailored exploit per application |
| Fix | Update the library in each application | Update the Java runtime each application uses |
| Known exploitation at disclosure | Yes, attacks seen before public disclosure | None reported as of disclosure day |
Java4Shell is harder to exploit and limited to certain CPUs, but that’s not a reason to wait. Modern cloud and data-center servers commonly use exactly the Intel and AMD processors that support AVX-512 VBMI, and patching Java is far easier than responding to a breach.
Are You Affected?
A system is exposed only when all three of these are true:
- It runs an affected Java version (OpenJDK 17.0.6 or later, 21, 25, or 27, from any vendor) that hasn’t been patched.
- It runs on an x86-64 CPU with AVX-512 VBMI.
- An application decodes Base64 from data an attacker can influence, which is common in web apps, APIs, and identity systems.
Check the CPU
On Linux, run:
grep -o -w -m1 'avx512vbmi' /proc/cpuinfo
If it prints avx512vbmi, the CPU supports the vulnerable instructions. If it prints nothing, this machine isn’t exposed to Java4Shell. Containers share the host’s CPU, so run this on the host or inside the container; the result is the same. In the cloud, the CPU depends on the instance type, so check each instance family you use.
Check the Java Version and Settings
Use the same Java installation, and the same options, that your application uses:
java -version
java -XX:+PrintFlagsFinal -version | grep -E ' (UseAVX|UseBASE64Intrinsics) '
Example output from Java 21 on a CPU without AVX-512:
openjdk version "21.0.13" 2026-10-20 LTS
int UseAVX = 2 {ARCH product} {default}
bool UseBASE64Intrinsics = true {product} {default}
The vulnerable code path is active only when the CPU has avx512vbmi, UseAVX is 3 or higher, and UseBASE64Intrinsics is true. In this example, UseAVX is 2, so this machine isn’t exposed even though the Java version is affected.
Don’t Forget Bundled Java
Many products ship their own Java runtime instead of using the system one, including some installations of Jenkins, Elasticsearch, Jira, Confluence, and Keycloak, and most Docker images. Check the Java version of each running process, not just java -version on the server. If the JDK’s jcmd tool is available:
jcmd <pid> VM.version
Replace <pid> with the process ID (from ps aux | grep java). New to these commands? See the Linux terminal guide.
How to Fix Java4Shell
1. Update Java
Install the patched release from your Java vendor. Oracle’s fixed versions are:
| Java line | Fixed Oracle 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-perf |
Other distributions, such as Eclipse Temurin, Amazon Corretto, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat, and Linux distribution packages, release patches on their own schedules and version numbers. Check your vendor’s security advisory rather than assuming Oracle’s version numbers apply.
2. Update Products That Bundle Java
For software like Jira, Confluence, Jenkins, Elasticsearch, or Keycloak, follow that vendor’s Java4Shell advisory. They may release new versions with an updated runtime, or tell you how to point the product at a patched Java.
3. Rebuild and Restart
- Restart every Java process after updating. A running process keeps using the old runtime until it restarts.
- Rebuild container images on a patched base image, then redeploy. Updating the host doesn’t fix Java inside containers.
- Prioritize internet-facing systems first: login pages, APIs, single sign-on, and anything reachable without authentication.
Temporary Mitigations If You Can’t Patch Yet
If you can’t update right away, you can turn off the vulnerable optimization with a JVM option. These are stopgaps, not fixes; remove them after patching.
| Option | What it does | Notes |
|---|---|---|
-XX:+UnlockDiagnosticVMOptions -XX:DisableIntrinsic=_base64_decodeBlock | Disables only the optimized Base64 decoder | Narrowest option |
-XX:-UseBASE64Intrinsics | Disables optimized Base64 encoding and decoding | Simple and widely cited |
-XX:UseAVX=2 | Disables all AVX-512 code in the JVM | Broadest; may slow other workloads. x86-64 only: Java on ARM won’t start with it |
Add the option to your application’s startup command or service configuration. Another way that’s often easier for services and containers is the JAVA_TOOL_OPTIONS environment variable, which every Java process reads at startup:
export JAVA_TOOL_OPTIONS="-XX:-UseBASE64Intrinsics"
Then confirm the setting took effect:
java -XX:+PrintFlagsFinal -version | grep -E ' UseBASE64Intrinsics '
Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsics
bool UseBASE64Intrinsics = false {product} {environment}
Base64 decoding still works with these options; it just uses the slower, regular Java code. A web application firewall or reverse proxy isn’t a reliable fix on its own, because Base64 shows up in too many places in normal traffic.
Detecting Problems
There’s no simple signature for Java4Shell attacks yet, but these steps help:
- Watch for unexpected JVM crashes. When Java crashes, it usually writes an
hs_err_pid<number>.logfile in the application’s working directory. Repeated crashes on an internet-facing service deserve investigation. - Review logs around any crash for unusual requests, especially to login, token, and API endpoints.
- Use your vulnerability scanner: major vendors are adding checks for CVE-2026-114938.
- Keep an eye on CISA’s Known Exploited Vulnerabilities catalog and your vendors’ advisories. If exploitation is confirmed, the urgency goes up.
If you find signs of compromise, follow the response steps in What Is a Cyber Attack?
What This Means for Developers
You can’t fix Java4Shell in your own code: the bug is in the Java runtime, below your application. Validating Base64 input doesn’t reliably help, since the bug is triggered during decoding. What you can do:
- Make Java updates routine. Pin your base images and runtimes to recent patch releases, and rebuild regularly.
- Know which Java your software runs on: keep an inventory of the runtimes inside your products and containers.
- Test your startup scripts with a mitigation option ready, so you can apply one quickly next time.
Timeline
| Date | Event |
|---|---|
| November 17, 2026 | Calif publishes the Java4Shell advisory; the OpenJDK project publishes an advisory and Oracle releases patched Java builds the same day |
| November 17, 2026 | Security vendors publish guidance; no exploitation in the wild reported, and no CISA KEV listing |
| Following days | Other Java distributions and product vendors release their own patched builds |
Frequently Asked Questions
What is Java4Shell?
Java4Shell (CVE-2026-114938) is a critical memory-corruption vulnerability in OpenJDK’s hardware-accelerated Base64 decoder. On x86-64 servers with AVX-512 VBMI, a malicious Base64 string can crash Java and, in some applications, allow remote code execution.
Is Java4Shell being exploited?
As of November 17, 2026, there were no public reports of exploitation in the wild, and it wasn’t in CISA’s KEV catalog. A proof of concept that demonstrates the bug is public, so that could change; patch now rather than waiting.
Am I affected if I use Java on a Mac or Windows laptop?
Apple silicon Macs aren’t affected, because they use ARM processors. Many laptop and desktop CPUs don’t support AVX-512 VBMI, but some do, so check your CPU. The bigger risk is servers that process internet traffic, but update Java on any machine anyway.
Are Java 8 and Java 11 affected?
Standard Java 8 and Java 11 releases aren’t listed as affected in the OpenJDK advisory. Oracle’s Java 8 Enterprise Performance Pack is affected and has its own fix (8u513-perf).
Is Java4Shell related to Log4Shell?
No. Log4Shell was a bug in the Log4j logging library. Java4Shell is in the Java runtime itself. Updating Log4j doesn’t fix Java4Shell; you need to update Java.
Is Java4Shell a zero-day?
No. Calif reported it to the vendors before going public, and Oracle’s fixes were released the same day it was disclosed, which is how coordinated disclosure is supposed to work. Systems that stay unpatched, though, are exposed to a now-public flaw.
Will the mitigation flags slow down my application?
Disabling the Base64 optimization makes Base64 decoding slower, which most applications won’t notice. -XX:UseAVX=2 disables more optimizations and may slow some workloads, so use it only if the narrower options aren’t available.
Conclusion
Java4Shell is a serious flaw in a core part of Java, but it has clear limits: it needs an affected Java version, an x86-64 CPU with AVX-512 VBMI, and an application that decodes Base64 from attacker-controlled input. Many servers meet all three conditions.
Check your CPUs and Java versions, update to a patched runtime from your vendor, rebuild containers, and restart every Java process. If you can’t patch today, apply one of the JVM mitigation options and remove it after you update. As with Log4Shell and PHP2Shell, the organizations that come through safely are the ones that know what they run and can patch it quickly.
Sources
- Calif. (2026, November 17). Java4Shell: Write once, RCE everywhere.
- Tenable. (2026, November 17). Java4Shell (CVE-2026-114938): Frequently Asked Questions About OpenJDK RCE Vulnerability.
- Endor Labs. (2026). Java4Shell (CVE-2026-114938): Pre-Auth Heap Overflow in OpenJDK.
- SentinelOne. (2026). Defending Against Java4Shell: Vulnerability in OpenJDK Enables RCE on AVX-512 CPUs.
