TL;DR
Java4Shell (CVE-2026-114938) affects Java 17.0.6 and later, on certain x86-64 systems. Update to your vendor’s fixed Java release; if you can’t update immediately, disable the affected optimization as a temporary mitigation.
On November 17, 2026, Oracle and the OpenJDK Vulnerability Group released fixes for CVE-2026-114938, known as Java4Shell. The vulnerability is a memory-corruption flaw in the hardware-accelerated Base64 decoder of the Java virtual machine (JVM). It was discovered and reported by the security research firm Calif, whose research shows that a remote, unauthenticated attacker can corrupt JVM memory. Calif reports having developed this into remote code execution against several widely used Java applications in their default configuration. Dynatrace has not independently verified those chains, and they have not been publicly released.
Base64 decoding is fundamental to Java applications. It is used in HTTP Basic authentication, JWTs, SAML messages, and cookies. The vulnerability therefore resides in the runtime itself and is independent of any particular library or framework.
Who is affected by Java4Shell (CVE-2026-114938)?
- Affected Java versions: Affected releases include Java 17.0.6 through 17.0.21, plus affected Java 21, 25, and 27 releases; fixed versions vary by distribution. Oracle’s Java 8 Enterprise Performance Pack is also affected. Standard Java 8 and Java 11 are not affected.
- Hardware precondition: The flaw is only reachable when the JVM runs on an x86-64 processor with AVX-512 VBMI support (Intel Xeon Ice Lake and later, AMD Zen 4 and later). On ARM64, the vulnerable code path is not used.
- Impact: Denial of service through a JVM crash is the most readily achievable outcome. Calif reports unauthenticated remote code execution against applications including Keycloak, Jira, Confluence, Artifactory, and Jenkins. These exploit chains have not been published, and no universal exploit exists; each target requires a dedicated chain.
- Severity: 8.1 (High) under CVSS 3.1, as scored by Oracle, and 9.2 (Critical) under CVSS 4.0, as scored by Calif.
- Exploitation: At the time of writing, scanning and exploitation attempts have been observed in the wild, but no successful exploitation has been publicly confirmed, and the CVE is not listed in the CISA Known Exploited Vulnerabilities catalog. A public proof of concept triggers the flaw without taking control of the system. Calif is withholding its full exploit chains to allow time for remediation.
What should you do about Java4Shell?
- Identify every Java runtime in your environment and determine which ones run an affected version and update to a fixed release of your distribution (see the table below). Updating is the only complete remediation.
- Apply an interim mitigation where an immediate update is not possible, by restarting the JVM with one of the flags described below.
What is the Java4Shell vulnerability?
To decode Base64 efficiently, the JVM uses a hand-optimized routine that relies on modern CPU instructions. On x86-64 processors with AVX-512 VBMI, this optimized path is enabled by default. Calif’s analysis shows that the routine mishandles certain malformed input and writes beyond the end of its output buffer. Although the JVM ultimately rejects the input, adjacent memory may already have been overwritten by that point.
A system is exposed when three conditions are met:
- It runs an affected Java version.
- The CPU supports the required AVX-512 features, so the optimized path is active.
- Attacker-controlled data can reach the Base64 decoder, which is the case for most internet-facing Java applications.
The CVE record refers to Oracle’s product names, but the flaw originates in OpenJDK. CERT-EU lists Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, BellSoft Liberica, SAP SapMachine, and the Red Hat build of OpenJDK among the affected distributions.
How to fix Java4Shell vulnerability (CVE-2026-114938)
Updating Java is the only complete remediation.
Java4Shell is fixed in Oracle/OpenJDK 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1.
Fixed versions for Oracle Java SE and Oracle OpenJDK:
| Release line | Affected versions | Fixed in |
| Java 17 | 17.0.6 and later, before 17.0.21.1 | 17.0.21.1 |
| Java 21 | Before 21.0.13.1 | 21.0.13.1 |
| Java 25 | Before 25.0.5.1 | 25.0.5.1 |
| Java 27 | Before 27.0.1.1 | 27.0.1.1 |
| Java 8 Enterprise Performance Pack (Oracle only) |
8u511b33-perf | 8u513-perf |
Other distributions: Consult your vendor’s advisory for the build that contains the fix, as build numbers differ between vendors. For example, Amazon lists Corretto 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, and 27.0.1.1.4 as fixed, and Red Hat tracks its packages in security bulletin RHSB-2026-018.
End-of-life versions: Vendor advisories cover supported release lines only. Unsupported release lines may contain the affected code, but status and patch availability vary by distribution. Treat them as potentially affected until the vendor confirms otherwise, and migrate to a supported release, since they will almost certainly not receive an official fix.
Interim mitigations
If you can’t update immediately, use one of these JVM flags as a temporary mitigation. Both require you to restart the JVM.
-XX:-UseBASE64Intrinsicsdisables hardware-accelerated Base64 encoding and decoding while leaving other CPU optimizations in place. This is the more targeted option and is recommended by Calif and AWS.Validate flag support with your exact JVM vendor/build in a staging environment. Unsupported flags may prevent startup; performance impact will vary by workload.-XX:UseAVX=2disables AVX-512 in the JVM entirely, which can reduce performance. Apply this flag on x86-64 hosts only: Calif warns that OpenJDK on ARM does not recognize it and fails to start.
References & sources
- Oracle: Critical Security Patch Update Advisory – November 2026
- OpenJDK Vulnerability Group: Advisory 2026-11-17
- Calif: Java4Shell: Write once, RCE everywhere
- CISA: Critical Java Vulnerability Requires Immediate Patching
- CERT-EU: Security Advisory 2026-021
- AWS: Security Bulletin 2026-189-AWS
- Red Hat: [CVE-2026-114938](https://access.redhat.com/security/cve/CVE-2026-114938)
For the status of Dynatrace products and the available updates, see the Dynatrace security alert for CVE-2026-114938.
Dynatrace is a trademark of the Dynatrace, Inc. group of companies. All other trademarks are the property of their respective owners.
Looking for answers?
Start a new discussion or ask for help in our Q&A forum.
Go to forum