Java4Shell: 64 A's and an equals sign can corrupt the JVM's memory
By Lior AharonovFounder, 7IT Solutions ·
What happened
On Tuesday 17 November, CISA urged organizations to patch CVE-2026-114938 in the Base64 decoder of the x86-64 HotSpot JVM immediately, saying crafted input could crash the JVM and allow unauthenticated remote code execution. BleepingComputer reports it hits OpenJDK 17.0.6 and later on AVX-512 x86-64 chips, and researchers got code execution on Jenkins, Jira and Keycloak in default setups.
Why it matters
Base64 is everywhere: the token, the file upload, the header your API decodes before it checks anything. CISA warns the runtime also hides inside third-party apps, container images and appliances, so the bug may sit in places nobody lists as Java.
What to do
Inventory every JDK, including the ones inside containers and vendor products, and install the patched build from Oracle or your vendor today. Until you can, BleepingComputer reports the researchers' stopgap is launching with -XX:-UseBASE64Intrinsics.

My take
Lior Aharonov
Founder, 7IT Solutions
The hardest part of a Java patch is never the patch. It's finding the runtime you forgot you shipped.
I've seen this before
I've seen this movie with Log4Shell, CVE-2021-44228. CISA reported active, widespread exploitation and told organizations to find every Log4j instance, internal software included, before patching. Same shape now: the inventory is the race.
Sources
| CISA: Critical Java Vulnerability Requires Immediate Patching | cisa.gov |
| BleepingComputer: Critical Java4Shell flaw allows RCE attacks on major Java applications | bleepingcomputer.com |
Researched with AI tools; every fact is checked against the linked sources.