Oracle and the OpenJDK project have patched Java4Shell (CVE-2026-114938), a memory-corruption flaw in the way Java decodes Base64 data on some modern x86-64 servers. Researchers say it can be turned into remote code execution against popular enterprise software without a login. No attacks have been reported yet, but patching has already started to matter.
What happened
Security firm Calif published details on November 17 after word of the bug leaked ahead of the planned disclosure. The flaw sits in hand-written assembly that OpenJDK uses to speed up Base64 decoding on processors with AVX-512 VBMI instructions. A malformed string ending in an extra padding character makes the routine write past the end of its output buffer. Java rejects the input afterward, but nearby heap memory may already be corrupted.
Calif says it demonstrated unauthenticated code execution, in default configurations, against Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate. It also showed code execution by authenticated attackers against Kafka, Solr, Elasticsearch, Gerrit and Spinnaker, and says both lists are incomplete. The researchers also describe a Heartbleed-style memory leak that could expose secrets and tokens held in the Java heap.
Oracle rates the flaw 8.1 (High) under CVSS 3.1 and notes high attack complexity; Calif scores it 9.2 (Critical) under CVSS 4.0. Oracle shipped fixes on November 17 in its November Critical Security Patch Update.
Who is affected
Calif says OpenJDK 17.0.6 and later is affected, along with Java 21, 25 and 27 and the distributions built from them, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK. Calif’s list also names an Oracle Java SE 8 performance build, so check your vendor’s notice for older lines.
Exploitation also needs x86-64 hardware with AVX-512 VBMI, such as Intel Xeon from Ice Lake onward and AMD Zen 4 or newer. ARM64 systems are not affected.
The risk is not uniform. Calif says there is no universal exploit, because each target needs its own steps. Firm VulnCheck says crashing a vulnerable JVM is easy, but a full exploit is much harder, and it does not expect the bug to be “easily or widely exploitable.” Cisco Talos had not seen exploitation as of SecurityWeek’s report and expects probing to pick up. Sophos also reports no known exploitation.
What to do
- Update Java as soon as your vendor ships a fixed build, then restart the applications so they load it. Sophos notes that other distributions are still releasing updates, and Endor Labs reported that the fix had not yet reached some public OpenJDK update repositories as of November 17.
- Find Java inside third-party products, containers and appliances. CISA, as reported by SecurityWeek, urged immediate patching and warned these copies may not appear in asset inventories.
- Check whether your servers have the CPU feature. On Linux, look for the
avx512vbmiflag; Calif also provides a command that checks four flags. - Prioritize internet-facing apps that decode Base64 from untrusted input, such as authentication headers, tokens and file uploads.
- If you cannot patch yet, Calif suggests starting the JVM with
-XX:-UseBASE64Intrinsicsor-XX:UseAVX=2. Sophos says Oracle and OpenJDK have published no workaround and that it has not validated these options, so test first. The second flag stops OpenJDK from starting on ARM, so use it only on x86-64 hosts.
Our analysis: treat the JVM flags as a stopgap on exposed systems, not a substitute for the update.
What we still do not know
Calif has held back its product-specific exploit chains and says it will publish them later. Its public proof of concept demonstrates the memory corruption but does not execute code. We do not know when every distribution will have a patched build, how the flaw leaked early, or whether attackers will find reliable paths against specific applications. Calif says AI helped it find and exploit the bug, taking about an hour to find it and two more hours to build a first working exploit.
Sources: Calif, Java4Shell write-up (Nov. 17, 2026); SecurityWeek (Nov. 18, 2026); Sophos advisory (Nov. 18, 2026).
Leave a Reply