Java4Shell: Critical Java Flaw Lets Attackers Run Code — Update Now
Java4Shell is a critical flaw in Java that can let an attacker run code on a server without logging in — but only on some systems. Tracked as CVE-2026-114938, it sits in OpenJDK’s Base64 decoder. Oracle released fixes on 17 November 2026. Servers on Java 17, 21, 25 or 27 with modern Intel or AMD…
Java4Shell is a critical flaw in Java that can let an attacker run code on a server without logging in — but only on some systems. Tracked as CVE-2026-114938, it sits in OpenJDK’s Base64 decoder. Oracle released fixes on 17 November 2026. Servers on Java 17, 21, 25 or 27 with modern Intel or AMD chips should update.
| Key fact | Detail |
|---|---|
| Flaw | CVE-2026-114938 — heap overflow (CWE-122) in OpenJDK’s Base64 decoder |
| Fixed | 17 November 2026, in Oracle’s November Critical Security Patch Update |
| Severity | Oracle: 8.1 (High), CVSS 3.1. Calif: 9.2 (Critical), CVSS 4.0 |
| Affected | Only x86-64 with AVX-512 VBMI CPUs, on affected Java builds |
| Not affected | ARM64 systems; x86-64 without AVX-512 VBMI; standard Java 8 and 11 |
| Exploitation | Attempts reported by 18 Nov 2026; no confirmed success; not on CISA’s KEV list |
| Fix | Update to 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1; restart every Java process |

What is Java4Shell, in plain English?
Java powers bank systems, telecom billing, government portals and tools such as Jira and Jenkins, all on the Java Virtual Machine (JVM). Base64 turns binary data into text for web requests, and Java decodes it constantly — logins, tokens, uploads — using a shortcut that runs special AVX-512 VBMI instructions.
Java4Shell is a bug in that shortcut. A crafted Base64 string ending with a stray equals sign makes the decoder miscalculate its output size, producing a negative length that lets it write far beyond the destination — Datadog found the write ran 62 bytes past a 98-byte array.

In the worst case, an attacker who shapes what sits next to the overwritten memory can run code on the server. Calif researchers Quang Luong and Albert Yang demonstrated this against default installations of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate, all without logging in.
Who is affected — and who is not
Java4Shell does not affect every Java installation. Three conditions must all hold: a vulnerable Java version, an AVX-512 VBMI processor, and attacker-controlled data reaching the decoder.
Java version: OpenJDK 17.0.6 and later, plus Java 21, 25 and 27. Standard Java 8 and 11 are not affected; Oracle’s Java 8 Enterprise Performance Pack is affected. Processor: the shortcut only runs on x86-64 processors with AVX-512 VBMI — Intel Xeon from Ice Lake onward and AMD Zen 4 or newer. Older servers and ARM64 systems are not affected.
| Java line | Affected versions | First fixed build |
|---|---|---|
| Java 17 | 17.0.6 through before 17.0.21.1 | 17.0.21.1 |
| Java 21 | All versions before 21.0.13.1 | 21.0.13.1 |
| Java 25 | All versions before 25.0.5.1 | 25.0.5.1 |
| Java 27 | All versions before 27.0.1.1 | 27.0.1.1 |
| Java 8 Enterprise Performance Pack | 8u511b33-perf | 8u513-perf |
Every OpenJDK-based distribution carries the same flaw, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK. End-of-life Java 18 to 20, 22 to 24 and 26 contain the same code and will get no fix, Cycode reports. On Linux, grep -om1 -E 'avx512[_]?vbmi' /proc/cpuinfo returning nothing means the CPU is not affected.
How bad is it? Two different severity scores
Oracle scores Java4Shell 8.1 out of 10 (High) under CVSS 3.1, noting high attack complexity. Calif scores it 9.2 out of 10 (Critical) under CVSS 4.0, reflecting demonstrated remote code execution without logging in.
The honest reading: dangerous on an exposed server, not a one-click catastrophe. Datadog found crashing the application is far easier than reliable code execution, and there is no single universal exploit for all Java applications. Still, attackers only need one working path — the Optimizely cyberattack that hit CNN, BBC and Zoom showed how one component can reach hundreds of sites at once.
Has Java4Shell been exploited yet?
As of 18 November 2026: attempts have been reported, but no successful exploitation has been confirmed. GreyNoise reported attempts but no confirmed success against its sensors. The Canadian Centre said it was not aware of active exploitation, while warning it could change quickly. The flaw is not on CISA’s Known Exploited Vulnerabilities list.
Working exploits exist behind closed doors: VulnCheck says one is available to its customers, and researcher Kevin Breen of Immersive says he built one — each must be adapted to its application. CISA published an alert on 17 November, and the Canadian Centre issued advisory AL26-029 the same day, urging immediate patching of internet-facing systems first.
How to fix it
The fix is straightforward, but it has one step people often miss: restart every Java process after updating.
Step 1 — Find every Java runtime. Check the version on each server, not just the Java on your command line — Jira, Jenkins, Keycloak and container images often bundle their own.
Step 2 — Update to a fixed build. For Oracle Java, install 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1, or your vendor’s fixed build. Rebuild container images and redeploy.
Step 3 — Restart and verify. Restart every Java service and confirm the running process reports the fixed build. Investigate any unexpected JVM crash since 17 November.

If you cannot patch immediately, use a workaround — temporarily. Starting the JVM with -XX:-UseBASE64Intrinsics switches off the fast Base64 code, as Keycloak recommended on 18 November. Alternatively, -XX:UseAVX=2 limits the JVM to AVX2 instructions, which Datadog confirmed prevented the out-of-bounds writes. But it applies only to x86-64: ARM64 JVMs do not recognise the flag and will fail to start. Patch as soon as you can.
What it means for Pakistan
There is no reported Java4Shell incident in Pakistan, and no Pakistani organisation has been named affected. The relevance is structural: Java runs widely in the systems Pakistan depends on — bank core systems, payment switches, telecom billing, government portals and university systems — many on modern x86-64 servers — the hardware this flaw needs.

For Pakistani developers and IT teams, check the Java bundled inside the products you bought, not just the Java you installed yourself — a patched server can still be exposed through an old Jira, Jenkins or Keycloak installation running its own runtime. Small teams should prioritise internet-facing services first and apply the -XX:-UseBASE64Intrinsics workaround today if patching must wait. When internet access is already fragile — as when Pakistan’s internet slowed by the SMW5 submarine cable fault — crashing Java services would be felt quickly. The Apple outage on 17 November and WhatsApp’s latest iPhone update show software updates are worth installing promptly.
Confirmed vs reported vs rumour
Confirmed: the flaw in OpenJDK’s AVX-512 Base64 decoder; Oracle’s fix on 17 November 2026; the affected and fixed versions; the CPU condition; both CVSS scores; the CISA alert.
Reported (credible, not independently reproduced): Calif’s unauthenticated code execution against six products; VulnCheck’s working exploit; GreyNoise’s attempts with no confirmed success; end-of-life Java versions with no fix coming.
Rumour (do not rely on): social-media claims of a public universal exploit or of organisations already breached. No such breach has been confirmed as of 18 November 2026.
What is not yet known — and when we will update
We do not yet know whether any organisation has been breached, when the first confirmed exploitation will appear, or how many exposed systems exist. We will update this article when CISA lists the flaw as exploited, when remaining vendors publish fixes, or when any confirmed breach is reported.
Frequently asked questions
What is Java4Shell?
CVE-2026-114938, a heap buffer overflow in OpenJDK’s Base64 decoder. A crafted Base64 string can make the decoder write past its memory, crashing Java applications or letting an attacker run code.
Which Java versions are affected?
OpenJDK 17.0.6 and later, and all Java 21, 25 and 27 releases before their fixed builds: 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1.
Am I affected if my computer runs on ARM, like Apple Silicon?
No — only x86-64 systems whose processors support AVX-512 VBMI. ARM64 systems, including Apple Silicon, do not run the vulnerable code.
Has Java4Shell been exploited in the wild?
As of 18 November 2026, attempts have been reported by GreyNoise, but no success confirmed; the flaw is not on CISA’s KEV list.
How do I check if my system is affected?
Check the Java version each service runs, including bundled runtimes, then the processor on Linux with grep -om1 -E ‘avx512[_]?vbmi’ /proc/cpuinfo.
What should I do if I cannot update Java right away?
Start the JVM with -XX:-UseBASE64Intrinsics, which switches off the vulnerable fast Base64 code. On x86-64 only, -XX:UseAVX=2 also disables the AVX-512 path — never on ARM64. Patch as soon as possible.
