Quick answer: Java4Shell (CVE-2026-114938) is a critical memory-corruption flaw in the Base64 decoder of Java’s x86-64 HotSpot virtual machine. Specially crafted Base64 input can crash Java or, in some conditions, let an unauthenticated attacker run code remotely. Oracle and OpenJDK released fixes on 17 November, and CISA says to patch immediately. Java 8 and 11, and ARM64 systems, are reported as unaffected.
The short version
- What: a Base64 decoding flaw in Java’s x86-64 HotSpot JVM
- Affected: Java 17 (from 17.0.6), 21, 25 and 27 on x86-64
- Fixed: Oracle’s 17 November update, e.g. 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1
- Exploited? No known attacks reported so far
What is Java4Shell?
It’s a vulnerability in the part of the Java Development Kit that decodes Base64 data on x86-64 systems. Security researchers say it sits in a hand-written, speed-optimised Base64 routine the JVM uses on processors with AVX-512. CISA describes it as a critical memory-corruption bug that “could crash the JVM and allow for unauthenticated remote code execution”.
Who found Java4Shell?
US security firm Calif said it discovered the bug, according to Reuters. The BBC reports that AI was used to find it.
Which Java versions are affected?
According to security researchers’ analysis of the advisories:
- Affected: Java 17 from 17.0.6, and Java 21, 25 and 27, on x86-64
- Not affected: Java 8 and 11, and ARM64 systems
Oracle’s 17 November update fixes it in Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Oracle, OpenJDK, Amazon Corretto, Azul Zulu and Microsoft’s OpenJDK builds have shipped fixes; some Linux distributions and other builds were still catching up at the time of writing. Check your vendor’s advisory for exact version numbers.
Is Java4Shell being exploited?
No known attacks had been reported at the time of writing. German and Dutch cyber agencies told Reuters there were no known successful attacks as of 18 November. That can change quickly, which is why agencies are urging immediate patching.
How do I protect my systems?
CISA’s advice, in short:
- Find every Java installation, including runtimes bundled inside other apps, containers and appliances.
- Patch, starting with internet-facing systems.
- If you can’t patch yet, validate Base64 input at the application boundary, set input-size limits and limit unauthenticated access.
- Watch for unexpected JVM crashes and unfamiliar Java processes.
Some security firms also describe a temporary workaround: starting the JVM with the Base64 intrinsics switched off, which may slow Base64-heavy workloads. Treat that as a stopgap, not a fix, and follow your vendor’s guidance.
Do home users need to do anything?
Java4Shell mainly affects servers and business systems. If you have Java on a PC, for example for Minecraft: Java Edition, keep it updated through its normal updater.
Is Java4Shell linked to the recent outages?
No. Reuters reports that authorities and companies haven’t connected it to this week’s outages, including the Apple outage and Microsoft’s Outlook problems.
Questions people ask
What is CVE-2026-114938?
Java4Shell, a critical flaw in Java’s Base64 decoder on x86-64 that can allow remote code execution.
Which versions fix Java4Shell?
Oracle’s 17 November update, including Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Check your vendor’s advisory for its own builds.
Is Java4Shell being exploited?
No successful attacks were known as of 18 November, according to German and Dutch agencies.
Who discovered Java4Shell?
US security firm Calif, according to Reuters.
Why is it called Java4Shell?
The name echoes Log4Shell, the 2021 Java logging flaw, signalling a similarly serious remote code execution risk.
Sources
- CISA: critical Java vulnerability requires immediate patching
- Microsoft: OpenJDK November 2026 critical patch update
- The Hacker News: CISA urges immediate patching
- Censys advisory
- Reuters
Where next
More security news this week: the Uber data breach at its AI vendor, Fireworks AI.
