Published 18 November 2026 · Rathish Kumar, Invitty
On 17 November 2026 Oracle and the OpenJDK project fixed CVE-2026-114938, nicknamed Java4Shell, a memory flaw in the JVM's Base64 decoding that needs no login. It affects Java 17.0.6 and later, plus 21, 25 and 27, on x86-64 servers whose CPUs support AVX-512 VBMI. Oracle's fixed builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Patch internet-facing Java applications first.
What Java4Shell is, in plain terms
Modern JDKs use a fast, CPU-specific routine to decode Base64 text. On processors with the AVX-512 VBMI instruction set, that routine can write past the end of its buffer when it is fed crafted input. Base64 is everywhere in web applications: login tokens, SAML assertions, file uploads and API payloads. So an attacker who can send text to your app may be able to reach the bug without an account.
Oracle scores it 8.1 under CVSS 3.1 and lists it as remotely exploitable without authentication. CISA put out an alert the same day, calling it a critical memory-corruption flaw. Calif, the research firm Oracle credits with the report, says it has shown pre-login code execution against default installs of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. Those product-specific exploits are being held back for now.
As of 17 November there is no confirmed exploitation in the wild. Calif has said the technical details leaked before the patch, and the root cause is now public. Our view: treat this like Log4Shell's younger cousin. The fix is a runtime upgrade, not a configuration change, and the hard part is finding every runtime.
Which Java versions and servers are affected?
Three conditions must line up: an affected Java build, an x86-64 CPU with AVX-512 VBMI, and untrusted data reaching the Base64 decoder. Per Qualys, that CPU feature appears on Intel Xeon from Ice Lake onwards and AMD EPYC and Ryzen from Zen 4. ARM64 servers, including AWS Graviton, are not affected. Standard Java 8 and Java 11, and anything older than 17.0.6, are also outside the scope.
| Java line | Affected Oracle build | Fixed build (17 Nov 2026) |
|---|---|---|
| Java 8 Enterprise Performance Pack | 8u511b33-perf | 8u513-perf |
| Java 17 | 17.0.21.0.3 and earlier, from 17.0.6 | 17.0.21.1 |
| Java 21 | 21.0.13.0.3 and earlier | 21.0.13.1 |
| Java 25 | 25.0.5.0.3 and earlier | 25.0.5.1 |
| Java 27 | 27.0.1.0.3 and earlier | 27.0.1.1 |
| GraalVM for JDK 17 and 21; GraalVM EE 21.3 | 17.0.21.0.3, 21.0.13.0.3; EE 21.3.20.0.3 | See Oracle's November CSPU |
Use the CPU check to decide what goes first, not what gets skipped. Cloud instances get resized and VMs move between hosts, so a safe server today may not be safe next quarter.
What about Temurin, Corretto, Zulu and bundled Java?
Oracle's builds only cover Oracle products. The OpenJDK advisory dated 17 November lists the same CVE as fixed in the upstream source, which is what Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft's build and Red Hat's packages are built from. Qualys reports that Amazon Corretto 17.0.21.1.2 was out on 17 November. Other distributions ship on their own schedules, so check each vendor's notice before you assume a build is fixed.
The bigger risk is Java you did not install yourself. Many commercial products carry a private JRE inside their install folder, and Linux package updates never touch it. Container images are the same: if a Dockerfile starts from an old JDK base image, the running pod keeps the flaw until someone rebuilds and redeploys it. CISA's alert makes the same point and asks organisations to inventory runtimes inside third-party software, images and appliances.
What to do, in order
- List every Java runtime. Run
java -versionon servers, search install folders for bundledjredirectories, and scan container registries for JDK base images. - Patch internet-facing logins first: identity servers such as Keycloak, then Jira, Confluence, Jenkins and Artifactory, then any Java app that accepts tokens or uploads from outside.
- Rebuild images on a fixed JDK base, push them, and redeploy. A patched registry is no use while old pods are still running.
- Where you cannot patch this week, researchers suggest starting the JVM with
-XX:-UseBASE64Intrinsics, which switches off the fast decoder. It needs a restart, may slow Base64-heavy work, and is not vendor-confirmed as a full fix. - Watch for JVM crashes and Java processes starting shells or making new outbound connections.
Oracle also says its fixed builds should not be used after the next Critical Patch Update on 19 January 2027, so put that date in the change calendar now.
What it means for Indian businesses
Most of the Java we see at Indian SMBs and SaaS firms is not a Java project anyone remembers: a Jenkins server, a self-hosted Jira, a Keycloak in front of a customer portal, or a vendor appliance. If one of those is exposed and later shows signs of compromise, CERT-In's directions require a report within 6 hours of noticing the incident, so keep notes of what you patched and when.
If you pay for Oracle Java SE subscriptions, the fixed builds are in your entitlement. If you moved off Oracle Java to a free OpenJDK build to save licence cost, that still works, but you now own the job of tracking each distribution's release. For teams running many containers, a base image that is rebuilt as soon as fixes land, such as Chainguard's container images, takes much of that tracking off your plate.
Next step
Send us a list of your Java applications, or let us scan for them. We will map each runtime to its fixed build, flag bundled JREs and stale images, and plan the restarts. Our container security team can rebuild and verify images, and a short VAPT after patching confirms your internet-facing apps no longer respond to the flaw.
Questions about Java4Shell
Is Java4Shell being exploited?
Are Java 8 and Java 11 affected by CVE-2026-114938?
Our servers run on ARM. Do we still need to patch?
Is there a workaround if we cannot upgrade Java this week?
Not sure if your devices are affected? Send us the model and current firmware or version on WhatsApp, or use the form on this page. We will tell you whether this advisory applies to you and which update to schedule.
Sources
Facts in this post come from these pages, checked on 18 November 2026. Vendors are still publishing fixed builds, so confirm the version for your distribution before you upgrade.
- Oracle Critical Security Patch Update Advisory, November 2026 (17 November 2026)
- OpenJDK Vulnerability Advisory, 17 November 2026
- Oracle JDK 17.0.21.1 release notes (17 November 2026)
- CISA alert: Critical Java vulnerability requires immediate patching (17 November 2026)
- Qualys: How to find, mitigate and patch Java4Shell (17 November 2026)
- The Hacker News: Oracle to patch 11 Java flaws as OpenJDK flaw report emerges (17 November 2026)