Key Takeaways
- Java4Shell, tracked as CVE-2026-114938, is a memory corruption flaw in OpenJDK's base64 decoder that Calif disclosed on November 17, 2026, and rated 9.2 out of 10 (critical), while Oracle scored it 8.1 (high).
- Calif said Java4Shell let it run code without logging in on Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins, and PingFederate in their default configurations, and said there is no universal exploit.
- Java4Shell affects OpenJDK 17.0.6 and later, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, and Red Hat OpenJDK, but only on x86-64 processors with AVX-512 VBMI support; ARM64 processors are not affected, according to Calif.
- Oracle fixed CVE-2026-114938 in its November 2026 Critical Security Patch Update on November 17, and CISA urged organizations the same day to patch immediately, starting with internet-facing systems.
What happened
Security firm Calif disclosed Java4Shell, tracked as CVE-2026-114938, on November 17, 2026, in a write-up on its website. The flaw is a memory corruption bug in the base64 decoder of OpenJDK, the open-source implementation of Java. Base64 is a common way of writing binary data as text, used in logins, file uploads, and network messages, Calif explained.
Calif said specially crafted base64 data can overwrite nearby memory. With careful exploitation, that can expose sensitive memory or let a remote attacker without credentials run code. Calif rated the flaw 9.2 out of 10 (critical). Oracle scored it 8.1 (high), BleepingComputer and SecurityWeek reported.
Oracle's advisory lists the flaw as exploitable over a network without authentication, but with high attack complexity, SecurityWeek reported. Calif made its findings public after news of the flaw surfaced ahead of the coordinated disclosure, according to SecurityWeek.
Calif researcher Quang Luong found the bug with OpenAI's Codex coding assistant during an audit of OpenJDK, BleepingComputer reported. Calif said finding it took Luong about an hour, and the first working exploit took two more hours, at an AI cost under $200. Oracle credits both Luong and Albert Yang with reporting the flaw.
Who is affected
In its own tests, Calif ran code without logging in on Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate, all in their default configurations. With a login, it ran code on Apache Kafka, Apache Solr, Elasticsearch, Gerrit, and Spinnaker. Calif said both lists are incomplete. It also showed the attack in sample applications built with Apache Struts and Spring Boot.
A Java program can also be compromised when it connects over TLS, the encryption used for secure web traffic, to a malicious server, even if it runs no service of its own, Calif said, citing an exploit from researcher samczsun.
Calif said Java4Shell affects OpenJDK 17.0.6 and later, and the Java builds based on it, including:
-
•
Oracle Java SE, Oracle OpenJDK, and Oracle GraalVM for JDK
-
•
Amazon Corretto and Eclipse Temurin
-
•
Microsoft Build of OpenJDK and Azul Zulu
-
•
BellSoft Liberica, SAP SapMachine, and Red Hat OpenJDK
The flaw is in code that runs only on x86-64 processors with AVX-512 VBMI, processor instructions that handle many bytes at once. Calif listed Intel Xeon processors from the Ice Lake generation onward and AMD EPYC and Ryzen processors with Zen 4 or newer as meeting that requirement. ARM64 processors are not affected.
There is no universal exploit, Calif said. An attacker has to find a way to deliver malicious base64 data to the decoder in each application. Security firm VulnCheck said crashing an affected Java service is easy once such a path is found, but running code is much harder, SecurityWeek reported. VulnCheck said it does not expect the flaw to be "easily or widely exploitable."
Patches and response
Oracle released fixes on November 17 in its November 2026 Critical Security Patch Update, which contains 655 new security patches, 11 of them for Oracle Java SE. The OpenJDK advisory of the same day lists Java 17, 21, 25, and 27 as affected. Oracle lists Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, and 27.0.1.0.3 as affected versions.
Users of other Java builds need patched releases from their own vendors, security firm Endor Labs said, according to SecurityWeek. As of November 17, the fix was not yet in the public OpenJDK 17, 21, and 25 update repositories, Endor Labs noted.
Calif published a proof of concept that shows the memory corruption but not code execution. It said it is holding back the attacks on individual products until users have had a chance to upgrade.
Cisco Talos said it had not observed attacks using the flaw, but expects probing to begin soon after public disclosure.
What organizations should do
The US Cybersecurity and Infrastructure Security Agency (CISA) urged organizations on November 17 to patch immediately. CISA advises organizations to:
-
•
Review software inventories for Java installations, including those bundled with third-party applications, container images, and appliances, which may not appear as separate entries.
-
•
Apply Java and vendor patches as soon as they are available, starting with internet-facing systems.
-
•
Where patching must wait, restrict and validate base64 input at the application boundary, enforce input size limits, and limit unauthenticated access.
-
•
Watch for unexpected Java crashes and suspicious Java processes.
For systems that cannot be updated right away, Calif and Talos describe a temporary workaround: starting Java with a setting that turns off the hardware-accelerated base64 code or AVX-512. The setting applies only to x86-64 machines; Java on ARM does not recognize it and fails to start. The exact settings are in Calif's write-up. BleepingComputer noted that these workarounds are temporary and that Java runtimes should be updated.