Java4Shell (CVE-2026-114938) is a critical memory-corruption flaw in the hardware-accelerated Base64 decoder of OpenJDK, affecting x86-64 servers with AVX-512 VBMI. This guide gives security and platform teams a five-step remediation path: find your exposure, apply a JVM flag mitigation, patch, prioritize by blast radius, and verify.
Java4Shell remediation comes down to four steps: find where affected Java runs, mitigate what you cannot patch today, patch, and verify. Java4Shell (CVE-2026-114938) is a memory-corruption flaw in the hardware-accelerated Base64 decoder in OpenJDK’s HotSpot VM. On x86-64 servers with AVX-512, it can let a remote attacker corrupt heap memory and potentially run code. Patches shipped on November 17, 2026. This guide walks through what to do, in order.
What Java4Shell is
The vulnerable code is an assembly-level optimization, called an intrinsic, that speeds up Base64 decoding using AVX-512 instructions. When the decoder receives a short input with unexpected trailing padding characters (=), it miscalculates a store mask. The result is a write of 62 bytes past the end of the output buffer before Java rejects the input as invalid. Researchers at Calif, who discovered the flaw, chained that out-of-bounds write into a heap leak and remote code execution.
Because Base64 carries login headers, tokens, and file uploads, the vulnerable path can run before a user has authenticated. Calif demonstrated pre-authentication remote code execution against Jira, Confluence, Keycloak, JFrog Artifactory, Jenkins, and PingFederate, and authenticated exploitation against Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Netflix Spinnaker.
Severity. The flaw is rated 9.2 (Critical) under CVSS 4.0, as cited by Calif, and 8.1 (High) under CVSS 3.1, the standard OpenJDK uses. These are the same assessment in two scoring systems. Treat it as critical.
Exploitation status. Calif has published its technical write-up and a bounded proof of concept that demonstrates the memory overwrite, but is withholding its product-specific exploit chains. As of November 18, Qualys reported no public exploit, and Azul reported no exploitation in the wild as of the evening of November 17 and that the CVE was not in CISA’s Known Exploited Vulnerabilities catalog. CISA has issued an alert urging immediate patching. Check current status before you set your deadline.
Who is affected
A system is exposed only when both conditions are true, and attacker-controlled data must also reach the Base64 decoding path.
| Condition | Affected | Not affected |
|---|---|---|
| Java runtime | OpenJDK-based builds from 17.0.6 onward, including 21, 25, and 27, from any vendor, unless patched | Releases before 17.0.6 (per Qualys, this includes standard OpenJDK 8 and 11), and builds that contain the fix |
| Processor | x86-64 with AVX-512 VBMI: Intel Xeon (Ice Lake through Granite Rapids) and AMD EPYC and Ryzen (Zen 4 and newer) | ARM64, and x86-64 without AVX-512 VBMI |
The affected list spans the major distributions, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, and Red Hat OpenJDK. For Azul products, Azul reports that Azul Core is affected on Java 17 (17.0.6 and later), 21, 25, and 27, and Azul Prime on Java 8, 11, 17, 21, and 25 in releases earlier than the fixed versions below. If you use a different distribution, check your vendor’s advisory.
Step 1: Find your exposure
Start with an inventory, because the runtime that matters is often one you did not choose. CISA warns that Java runtimes bundled with third-party applications, container images, and appliances may not appear as separate entries in software inventories.
- Check the hardware. On Linux, run the command below. If all four flags appear, the host can take the vulnerable code path.
- Find the Java runtimes. List every JDK and JRE across hosts, containers, and bundled applications, and note the version and vendor.
- Cross the two lists. Affected runtime plus AVX-512 VBMI hardware equals in scope.
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
Azul Runtime Inventory, part of Azul Intelligence Cloud, shows which Java runtimes you run in production and whether each is on the latest security update, which shortens the inventory step.
Step 2: Mitigate what you cannot patch today
If testing and rollout will take time, a JVM flag can close the exposure in the meantime. Both options are documented by Calif and Wiz:
- -XX:-UseBASE64Intrinsics disables the hardware-accelerated Base64 intrinsics. This is the recommended workaround.
- -XX:UseAVX=2 disables AVX-512 execution. Use it only on x86-64 hosts: OpenJDK on ARM does not recognize it and will fail to start.
Both can affect performance. Running applications also keep the vulnerable code until they restart, so schedule restarts, beginning with internet-facing identity, CI/CD, and collaboration systems.
Be cautious about network-layer substitutes. Web application firewalls may block some exploit patterns, but because the flaw is in the runtime, many code paths can reach it, and Wiz notes that WAF rules are unlikely to cover them all. Calif likewise notes that request buffering, which defeats some of its grooming techniques, is not a general mitigation. Treat these as extra layers, not fixes.
Step 3: Patch
Oracle released its patch on November 17, 2026, at the time of the OpenJDK advisory. Downstream vendors followed with their own builds, so apply the update from the vendor that supplied each runtime.
For Azul customers:
- Azul Core: the fix is in the November 2026 Critical Security Patch Update (CSPU) builds, available both on Azul’s Security-only, Stability-first line and on its full Patch Set Update (PSU) line.
- Azul Prime: upgrade to 26.08.110.0 or 26.02.510.0.
- The same update fixes 10 other CVEs that affect every Java version Azul supports.
Azul says it shipped the November CSPU within an hour of the coordinated release, and that Java4Shell is not a zero-day: it was reported through the OpenJDK vulnerability process and fixed in the scheduled November update.
Step 4: Prioritize by exposure and blast radius
You will rarely patch everything at once. Work in this order:
- Internet-facing systems that handle identity, builds, and collaboration: Keycloak, PingFederate, Jenkins, Artifactory, Jira, and Confluence were the demonstrated pre-authentication targets. A compromise here can expose everything that trusts those identities, tokens, and artifacts.
- Other internet-facing Java services on AVX-512 hardware.
- Internal services, ranked by data sensitivity and by whether untrusted data can reach them.
- Java clients. Calif reports a client-side exploit in which a Java program is compromised by connecting over TLS to a malicious server.
Also remember that the flaw can crash a JVM, so availability is at risk even where code execution is hard.
Step 5: Verify and keep watching
- Confirm that each patched host now reports the fixed version, and that restarted processes are running the new runtime.
- Re-run the hardware and version cross-check to find stragglers, including bundled and containerized runtimes.
- Watch vendor advisories and CISA for updates, since exploit status can change quickly.
- Review logs on exposed services for malformed Base64 input and unexpected JVM crashes.
Why the clock matters: AI is shortening the window
AI does not replace your enterprise infrastructure; it amplifies the pressure on it, and security is where that pressure now shows up fastest. Calif says it found this bug with AI assistance and that AI agents built most of its exploit chains. Wiz reports that its AI research harness built a working proof of concept in about two hours, although generalizing an exploit across arbitrary targets remains difficult. Azul’s 2026 AI Vulnerability Gap Report found that 69% of surveyed security leaders believe an attacker with AI can build a working exploit in three days or less, while only 13% say their organization can deploy a critical patch in under 24 hours. Azul also cites a median enterprise patch cycle of 43 days. The distance between how fast exploits can be built and how fast patches are deployed is where risk accumulates.
How Azul helps with Java4Shell remediation
Azul Zulu builds of OpenJDK are on the affected list, and Azul says so plainly. What matters is how fast a fix reaches production safely, because the Java platform you run determines your security outcomes at scale.
- Security-only, Stability-first updates. Azul Core offers quarterly, monthly, and out-of-cycle updates that contain security fixes only, with no new features or unrelated bug fixes. They are built on the previous quarter’s stabilized update, so teams can deploy them with less regression risk, which helps close the patch gap.
- Support and protection. Azul Core comes with 24x7x365 support from Java experts and IP protection and indemnification commitments.
- Visibility. Azul Runtime Inventory helps you find which runtimes you run and whether they are current. Azul Intelligence Cloud’s Vulnerability Detection uses production runtime data to focus remediation on code that actually runs.
If you need help getting patched, Azul’s patching guidance is a good place to start.
Frequently asked questions
Is Java4Shell a zero-day?
Per Azul, no. It was reported through the OpenJDK vulnerability process, and the fix shipped in the scheduled November 17 update. Details of the CVE became public shortly before the coordinated release, which led some teams to ask. Calif published its technical write-up after patches shipped.
Does Java4Shell affect ARM servers?
No. The vulnerable code is specific to x86-64 processors with AVX-512 VBMI. ARM64 is not affected.
What is the fastest temporary Java4Shell mitigation?
Start the JVM with -XX:-UseBASE64Intrinsics, then restart the application. Use -XX:UseAVX=2 only on x86-64 hosts.
Do I still need to patch if I apply the flag?
Yes. The flag buys time but does not replace the update.
Which applications are most at risk?
Researchers demonstrated pre-authentication remote code execution on Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate in default configurations, and noted that the list is not exhaustive.