---
title: "Java4Shell (CVE-2026-114938): Detecting the Critical OpenJDK RCE Hiding in Your Java Runtimes"
url: "https://www.armorcode.com/blog/java4shell-cve-2026"
markdown_url: "https://www.armorcode.com/blog/java4shell-cve-2026.md"
llm_canonical: "https://www.armorcode.com/blog/java4shell-cve-2026.md"
canonical_for_llm: true
entity_type: "Article"
primary_entity: "Java4Shell (CVE-2026-114938): Detecting the Critical OpenJDK RCE Hiding in Your Java Runtimes"
citation_value: "Published on ArmorCode; canonical URL https://www.armorcode.com/blog/java4shell-cve-2026."
last_updated: "2026-11-18T13:35:53-08:00"
---

<h1>Java4Shell (CVE-2026-114938): Detecting the Critical OpenJDK RCE Hiding in Your Java Runtimes</h1>

<h2>What is Java4Shell (CVE-2026-114938)</h2>

On November 17, 2026, researchers at Calif, who also disclosed [PHP2Shell](https://www.armorcode.com/blog/php2shell-rce), disclosed **Java4Shell (CVE-2026-114938)**, a memory-corruption vulnerability in the Base64 decoder of OpenJDK’s x86-64 HotSpot JVM. [Calif](https://calif.io/java4shell) rates it **CVSS 4.0 9.2 (Critical)**, and Oracle’s own score is CVSS 3.1 8.1 (High). A remote attacker with no credentials can overwrite heap memory, leak it in the style of Heartbleed, and reach remote code execution. Oracle shipped patches the same day, and **CISA** issued an alert urging organizations to patch immediately.

The flaw sits in the runtime and not in any one application, and Java is bundled inside many products without its own inventory entry, so finding it matters as much as patching it.

<h2>How the Java4Shell Base64 flaw works</h2>

To decode Base64 quickly, OpenJDK uses AVX-512 VBMI instructions on supported x86-64 processors. The bug is in the hand-written assembly that handles the final few characters. For malformed input ending in padding, the code computes a negative output length, which turns into a full 64-byte write that runs past the end of the result array. Java later rejects the input, but by then neighboring heap objects may already be corrupted. Calif turned this into a heap leak and code execution through careful heap grooming.

<h2>Who is affected by Java4Shell</h2>

| **Condition** | **Detail** |
| --- | --- |
| Runtime | OpenJDK-based runtimes from 17.0.6 and newer, including every later release. Oracle also lists one Java 8 performance build (8u511b33-perf). Standard Java 8 and 11 are reported as not affected. |
| Distributions | Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle OpenJDK, Oracle Java SE and Oracle GraalVM for JDK |
| Hardware | x86-64 CPUs with AVX-512 VBMI, such as Intel Ice Lake and newer Xeons and AMD Zen 4 or newer. ARM64 is not affected. |
| Reachability | The application must decode attacker-influenced Base64, which authentication, file upload and network-message features often do |

<h2>Which Java versions are affected by Java4Shell?</h2>

Oracle lists these Java SE versions as vulnerable, with fixes reported in the November 2026 update.

| ****Product**** | ****Affected version range**** | ****Fixed version**** |
| --- | --- | --- |
| Oracle Java SE 8 and 11 | Not affected (Oracle lists one Java 8 performance build, 8u511b33-perf) | — |
| Oracle Java SE 17 | Java 17 releases before 17.0.21.1 | 17.0.21.1 |
| Oracle Java SE 21 | Java 21 releases before 21.0.13.1 | 21.0.13.1 |
| Oracle Java SE 25 | Java 25 releases before 25.0.5.1 | 25.0.5.1 |
| Oracle Java SE 27 | Java 27 releases before 27.0.1.1 | 27.0.1.1 |
| Eclipse Temurin | Java 17 through 17.0.21+9, 21 through 21.0.13, 25 through 25.0.5+8, and earlier | No confirmed fix |
| Amazon Corretto | Java 17 through 17.0.21.0.11, 21 through 21.0.13.0.11, 25 through 25.0.5.0.10, 27 through 27.0.1.0.11, and earlier | 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, 27.0.1.1.4 |
| Oracle GraalVM (JDK and Enterprise) | CVE-specific affected range not confirmed | Not confirmed |

**Fixed builds differ by vendor, so check your distribution’s advisory before patching.**

<h2>How risky is Java4Shell right now?</h2>

- **Real applications are exposed.** In default configurations Calif demonstrated pre-authentication RCE against Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate, and post-authentication RCE against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. Java clients that connect over TLS to a malicious server are also at risk.
- **No universal exploit.** Each target needs its own exploitation profile, and failed attempts can crash the JVM. Calif is withholding product-specific exploits until people can upgrade, but it published a bounded proof of concept for the trigger.
- **No confirmed exploitation yet.** As of November 18, 2026, the CVE is not in CISA’s Known Exploited Vulnerabilities catalog and we have seen no confirmed in-the-wild activity. Treat that as a short window.

<h2>Why version-only queries miss Java4Shell</h2>

- **The runtime is often invisible.** CISA notes that JDKs and Java runtimes may not appear as separate inventory entries. They are bundled in third-party applications, container images and appliances.
- **Version strings differ by vendor.** Corretto, Temurin, Zulu and others use their own build numbers, so a single version comparison produces noise.
- **Hardware decides exposure.** The CPU requirement is invisible to most scanners, and many cloud instance families use affected processors, so cloud Java workloads are as likely to be exposed as on-prem ones. Two hosts with the same Java version can differ in exposure.
- **Dependency scanners miss it.** The flaw is in the runtime and not in a library, so updating application libraries does not help. Only replacing the runtime and restarting the JVM does.

Map findings by **CVE-2026-114938**, and use runtime version, CPU and internet exposure as secondary filters for prioritization.

<h2>How to detect Java4Shell in your environment with <strong>ArmorCode</strong></h2>

<h3>1. Ask Anya</h3>

Start with Anya, ArmorCode’s AI security champion, where you can ask targeted questions such as:

- Am I impacted by CVE-2026-114938?
- Show me all applications, services, and workloads exposed to CVE-2026-114938.
- Am I vulnerable to the Java4Shell Vulnerability (CVE-2026-114938)?

<h3>2. Findings Page</h3>

- Navigate to the Findings page to access the pre-configured saved view, “Java4Shell Nov 2026”. By consolidating results around the CVE ID, it unifies findings from all connected scanners into a single triage workflow. Prioritize remediation by sorting assets according to their criticality and internet exposure.

<h2>How to fix Java4Shell: patch, restart or apply a JVM flag</h2>

1. **Inventory every Java runtime,** including those bundled in products, container images, appliances and trimmed jlink runtimes. Search for the JVM library itself (libjvm.so or jvm.dll), not only a java binary on the PATH, since some products run a JVM with no process named java. Start with internet-facing systems that accept untrusted input.
2. **Patch and restart.** Apply the November 2026 Oracle or your vendor’s OpenJDK update, rebuild container images, and restart every affected JVM. Ask vendors whether the runtime bundled with their product is fixed.
3. **If you cannot patch, apply a JVM flag.** Start the JVM with -XX:-UseBASE64Intrinsics to turn off the optimized Base64 code (for example through JAVA_TOOL_OPTIONS), or -XX:UseAVX=2 to turn off AVX-512. Use the second flag only on x86-64 hosts, since ARM JVMs will not start with it. Confirm the flag reached the running process, recreate containers instead of restarting them so they pick up new environment variables, and record the host as mitigated, not fixed.
4. **Add compensating controls.** Per CISA, validate Base64 input at the application boundary, enforce size limits and limit unauthenticated access. 
5. **Check the CPU, but patch regardless.** On Linux, run lscpu | grep -i avx512 and look for avx512vbmi. On Windows, run coreinfo.exe -f. On Kubernetes, check the node label feature.node.kubernetes.io/cpu-cpuid.AVX512VBMI. Because exposure is hard to establish reliably, update affected Java versions whatever the CPU.
6. **Review logs for signs of attempts.** Look for unexplained JVM crashes (hs_err_pid files), bursts of IllegalArgumentException from java.util.Base64$Decoder, rogue runtimes, and Java processes spawning shells or download tools. These are leads, not proof. Their absence does not show that a system is patched or untouched, because a memory-corruption exploit may leave little behind.

<h2>Key Takeaways</h2>

- **What it is:** Java4Shell (CVE-2026-114938) is a critical memory-corruption flaw in the Base64 decoder of OpenJDK’s x86-64 HotSpot JVM that Calif says can lead to unauthenticated remote code execution (RCE).
- **Who is affected:** OpenJDK-based runtimes from 17.0.6 onward, including Amazon Corretto, Eclipse Temurin and Oracle Java SE, on x86-64 CPUs with AVX-512 VBMI. ARM64 is not affected.
- **How to fix it:** Update to your vendor’s November 2026 release, rebuild container images and restart every JVM. Fixed builds differ by vendor.
- **Interim mitigation:** If you cannot patch, start the JVM with -XX:-UseBASE64Intrinsics, or -XX:UseAVX=2 on x86-64 hosts only. Treat those hosts as mitigated, not fixed.
- **How to find your exposure:** Search by CVE ID in ArmorCode with Anya or the “Java4Shell (Nov 2026)” view. Bundled runtimes and vendor-specific version strings make version-only queries unreliable.

<h2>References</h2>

- **CISA:** [Critical Java Vulnerability Requires Immediate Patching](https://www.cisa.gov/news-events/alerts/2026/11/17/critical-java-vulnerability-requires-immediate-patching)
- **Calif:** [Java4Shell: Write once, RCE everywhere](https://calif.io/java4shell)
- **OpenJDK:** [Vulnerability advisory, November 17, 2026](https://openjdk.org/groups/vulnerability/advisories/2026-11-17)
- **Oracle:** [Critical Patch Update, November 2026](https://www.oracle.com/security-alerts/cspunov2026.html)
