Security advisory: Critical remote code execution vulnerability in Java (“Java4Shell”)
Published: November 18, 2026
CVE-2026-114938 | Oracle Java SE November 2026 Security Update
Severity: Critical (CVSS v4.0 9.2)
Status: Partial fixes; mitigate now
Fixed builds are available from Oracle, Amazon Corretto and Azul Zulu. Eclipse Temurin, Microsoft, Red Hat, Debian, Ubuntu and most bundled application runtimes are not yet fixed. Apply the startup setting below until they are.
Topics on this page:
Summary
On November 17, Oracle released 11 Java SE security fixes, and research firm Calif disclosed the most serious of them: CVE-2026-114938, known as “Java4Shell.” It is a memory-corruption flaw in Java’s hardware-accelerated Base64 decoder. Because Base64 carries login headers, tokens and uploads, the flaw is often reachable before login. CISA and the Canadian Centre for Cyber Security (alert AL26-029) both urge prompt patching.
Calif demonstrated unauthenticated remote code execution against default installations of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate, and code execution after login against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. Even without code execution, it can leak keys, tokens and personal data from memory, and crashing an affected service is reported to be easy. Java clients connecting to a malicious TLS server can also be attacked.
Exposure is narrower than the headlines suggest: only Java 17.0.6 and later, on x86-64 processors with AVX-512 VBMI. Java 8 and 11, ARM and older x86 processors are not affected.
Exploitation status: no successful attacks have been confirmed, and the CVE is not on the CISA KEV catalogue. However, GreyNoise has recorded a small number of exploit-shaped requests, unverified exploit code is appearing online, and researchers expect targeted attacks on high-value identity, build and collaboration servers.
What is known so far
| Field | Detail |
|---|---|
| CVE | CVE-2026-114938 (“Java4Shell”), one of 11 Java SE fixes in Oracle’s November 2026 Critical Security Patch Update. |
| Severity | Critical. CVSS v4.0 9.2 (Calif and OpenJDK); CVSS v3.1 8.1 (Oracle). |
| Impact | Heap overflow in the AVX-512 Base64 decoder. Can crash the JVM, leak heap memory, or, with an application-specific exploit, allow unauthenticated code execution. |
| Affected | Java 17.0.6 and later, including 21, 25 and 27, from any vendor, plus Oracle’s 8u511-perf build. Only on x86-64 processors with AVX-512 VBMI: Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4 and newer. |
| Not affected | Standard Java 8 and 11; Java 17.0.0 to 17.0.5; ARM64; x86 processors without AVX-512 VBMI (e.g. Cascade Lake, AMD before Zen 4). |
| Exploit status | None confirmed. Calif is withholding its exploits; treat public repositories claiming one as suspect and possibly malicious. |
Fixed builds
| Java runtime | Fixed build | Notes |
|---|---|---|
| Oracle Java SE | 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1; 8u513-perf | Also fixes Oracle’s other 10 Java SE flaws. |
| Amazon Corretto | 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 | Amazon Linux packages also released. |
| Azul Zulu | 17.0.21.1, 21.0.13.1, 25.0.5.1 | |
| Eclipse Temurin, Microsoft Build of OpenJDK | Not yet released | Current Temurin builds are confirmed vulnerable. |
| RHEL 8, 9, 10 and Red Hat build of OpenJDK | Not yet released | Rated Critical (RHSB-2026-018); includes UBI images and OpenShift. |
| Debian and Ubuntu packages | Not yet released | Updating packages will not fix this today. |
| Bundled runtimes (Jira, Jenkins, Keycloak) | From the product vendor | No fixed Keycloak image yet; no Atlassian, Jenkins or Ping guidance at the time of writing. |
Recommendations
- Find every running Java runtime. Check the runtime each process actually uses, not just the system java: jcmd
VM.version or readlink -f /proc/ /exe. Many products bundle a runtime that OS updates do not touch (affected ones are reported in Omnissa Horizon and UniFi Network), as do container images. - Check the processor as the server sees it. On Linux, grep -o -w avx512vbmi /proc/cpuinfo prints nothing on unaffected processors. Do not rely on lscpu | grep avx512, which also matches older, unaffected processors. For VMs, check inside the guest, since the hypervisor’s CPU settings decide exposure and a migration can change it. Use this to prioritize, not to close findings.
- Patch where a fixed build exists. Restart every Java process and rebuild images, then confirm the running process uses the new build.
- Otherwise, apply the startup setting today. Add -XX:-UseBASE64Intrinsics to the JVM options and restart. It turns off the vulnerable decoder on any architecture; Base64-heavy workloads may slow. Confirm with jcmd
VM.flags. Where to add it: - Jira and Confluence: JVM_SUPPORT_RECOMMENDED_ARGS in setenv.sh or setenv.bat. Jenkins: JAVA_OPTS.
- Keycloak containers: JAVA_OPTS_APPEND. Other containers: JAVA_TOOL_OPTIONS. Append to existing values rather than replacing them.
- Avoid the alternative -XX:UseAVX=2 in configuration shared with ARM hosts, where Java will refuse to start.
- Work in priority order. Internet-facing identity providers (Keycloak, PingFederate) first; then Jira, Confluence, Jenkins and Artifactory; then other internet-facing Java services handling logins, tokens or uploads; then internal systems and Java clients such as build agents. If you can neither patch nor mitigate, restrict access to the VPN or trusted networks.
Monitoring & detection
Failed attempts often crash the JVM, so crashes are the likeliest early sign. Alert on:
- Crashes. New hs_err_pid*.log files or repeated restarts of internet-facing Java services.
- Decoder errors. Bursts of IllegalArgumentException from java.util.Base64$Decoder in application logs.
- Suspicious input. Base64 values of 32 or more characters ending in “=” whose length is not a multiple of four, especially in Authorization headers.
- Post-exploitation. Java processes starting shells or making unexpected outbound connections.
References
- Oracle Critical Security Patch Update, November 2026
- OpenJDK Vulnerability Advisory, 2026/11/17
- Canadian Centre for Cyber Security, AL26-029
- CISA: Critical Java Vulnerability Requires Immediate Patching
- Calif: Java4Shell technical write-up
- Red Hat Security Bulletin RHSB-2026-018
- Keycloak Java4Shell advisory
- GreyNoise Java4Shell activity dashboard
Support
As always, please let us know if you have any questions or concerns or see unusual activity on your systems that you believe might be associated with this or any other vulnerability. Please send these communications to security.response@utoronto.ca.
