Java4Shell can let outsiders run code on OpenJDK without signing in
CISA told organizations to install Oracle’s November Java fixes immediately and, if that must wait, to limit Base64 input and access that skips login. Cisco Talos has not seen attacks yet and expects scans after the disclosure.
A flaw nicknamed Java4Shell can let someone who never signs in run their own commands on servers that use affected OpenJDK builds, by sending the runtime a crafted Base64 string. CISA is pressing organizations to patch at once: the bug is a memory-corruption flaw in the Base64 decoder of the x86-64 HotSpot virtual machine inside the JDK, and a crafted string could crash that runtime as well as open a path to code execution.
Cisco Talos tracks it as CVE-2026-114938 and scores it 9.2 on CVSS 4.0. Talos says it reaches OpenJDK releases from 17.0.6 onward on x86-64 processors that have AVX-512 VBMI enabled, a feature on many Intel and AMD chips, in on-premise setups and in the cloud. ARM64 systems are outside that path. Talos said tests had already succeeded against a set of Java applications and that further targets may be confirmed. Calif Research, which Talos thanked as Calif.io for an advance look, says OpenJDK underpins software in banks, aviation and telecom, and by Calif’s count runs at 90% of Fortune 500 firms.
How a short Base64 string breaks the decoder
Calif Research describes the fault in hand-written processor instructions OpenJDK uses to decode Base64 faster. The input that breaks it is 64 A characters plus one equal sign, the character Base64 adds as padding when a block is incomplete. The decoder miscalculates a length and stores 64 bytes in a buffer sized for as few as 50, overwriting adjacent memory. The program rejects the input only after that write. Alone, the damage usually crashes the process. Calif Research said an attacker who first lays out nearby memory, a technique called heap grooming, can turn the corruption into control of the server, and can read nearby data in a way the group likened to the 2014 Heartbleed bug.
The group said code execution without a login was shown in Jenkins, Keycloak, Confluence, Jira and PingFederate, with a working intrusion against Keycloak. Where a valid account was required, the same class of attack was shown in Kafka, Solr and Elasticsearch. Researcher samczsun found that merely connecting to a hostile server can also compromise Java programs. Much of the hunting, Calif Research said, was done with AI coding tools.
Fixes, and what to do if a patch must wait
Oracle’s advance notice listed 11 Java SE flaws that could be reached remotely with no login, with a maximum CVSS 3.1 score of 8.1, and those patches were due on Tuesday, November 17, 2026. Oracle then shipped a fix for Java4Shell the same day as a November update covering 652 flaws, CyberScoop reported. CISA tells defenders to follow Oracle’s November 2026 critical patch advisory, install Java and vendor fixes once those updates can be installed, and start with systems exposed to the internet.
Talos has not seen the bug used in attacks beyond research, but it expects probing to rise after the public write-up. If a patch cannot go in immediately, Talos says start the JVM with AVX-512 disabled via the flag =XX:UseAVX=2. That option is only for x86-64; ARM hosts will not recognize it and the application may fail to start. CISA’s stopgaps are to check and constrain Base64 where it enters the application, cap input size, and reduce access that does not require a login. Inventories should cover JDKs bundled in other software, container images and appliances, since those copies may not appear as their own entries. Watch for unexpected JVM crashes, suspicious Java processes and rogue runtimes. Talos published Snort rules, including a free community set, that look for bad Base64 in particular HTTP request fields tied to this bug. Cisco said it is still reviewing its own products and will post updates shortly. The Canadian Centre for Cyber Security helped prepare the CISA alert.