Calif · 2026-11-17 · major
Java4Shell — Codex found a remote-code bug in Java for under $200
In short
Java4Shell (CVE-2026-114938) is a remote code execution bug in OpenJDK's Base64 decoder. Calif says Codex found it in about an hour for under $200 in tokens. OpenJDK and Oracle shipped fixes on November 17.
Calif · 2026-11-17 · 4 sources checked

An AI agent found a pre-auth RCE in Java's Base64 decoder in an hour; patch every JDK you run.
Key specs
| Cvss 4.0 | 9.2 |
|---|---|
| Token cost | < $200 |
Quick facts
| CVE | CVE-2026-114938 |
|---|---|
| Affected | OpenJDK 17.0.6 and newer, on x86-64 CPUs with AVX-512 VBMI |
| Not affected | ARM64 |
| Found with | Codex, in about one hour |
| Oracle fixed builds | 8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 |
| Stopgap | -XX:-UseBASE64Intrinsics |
What is it?
Java4Shell (CVE-2026-114938) is a memory-corruption bug in hand-written x86-64 assembly that OpenJDK's HotSpot uses to speed up Base64 decoding with AVX-512 VBMI instructions. The security firm Calif disclosed it on November 17, 2026, the same day OpenJDK and Oracle released fixes, and rates it 9.2 (Critical) under CVSS 4.0.
How does it work?
A short padded Base64 input makes the fast decoder write past the end of a small buffer, which an attacker can turn into code execution. Calif's Quang Luong pointed Codex at the JIT compiler, intrinsics, widely used APIs and cryptography; the agent reported the Base64 flaw after about an hour, and a working exploit took about two more hours. Calif demonstrated pre-auth RCE against default setups of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate.
Why does it matter?
Almost every company runs Java on servers with recent Intel Xeon or AMD Zen 4+ chips, so the exposure is wide, including JDKs bundled in containers and apps. The case also shows how cheap AI-assisted bug hunting has become: under $200 in tokens for a critical bug in one of the most-audited runtimes. Teams should update each Java line to its fixed build, or start the JVM with -XX:-UseBASE64Intrinsics until they can.
Who is it for?
anyone running Java servers
Frequently asked questions
- Which Java versions are vulnerable to Java4Shell?
- Calif says Java4Shell affects OpenJDK 17.0.6 and newer, and the bug is present in builds from Amazon Corretto, Eclipse Temurin, Microsoft, Azul Zulu, BellSoft, SAP, Red Hat and Oracle. It only triggers on x86-64 CPUs with AVX-512 VBMI, such as Intel Ice Lake or newer Xeons and AMD Zen 4 or newer. ARM64 machines are not affected.
- How can I protect a Java server from Java4Shell if I cannot patch today?
- Calif lists two temporary mitigations for Java4Shell: start the JVM with -XX:-UseBASE64Intrinsics, or on x86-64 hosts only with -XX:UseAVX=2, which avoids the vulnerable AVX-512 code path. Calif warns that ARM OpenJDK will not start with the UseAVX flag, and that nginx request buffering is not a general mitigation.
- Is Java4Shell being exploited in the wild?
- Aikido Security reported no exploitation of Java4Shell as of November 17, 2026. That may change quickly: Calif published its technical write-up after the patches shipped, and its demonstrations show pre-auth remote code execution against common products such as Jenkins, Jira, Confluence and Keycloak, so internet-facing Java services should be patched first.
- How much did it cost to find Java4Shell with AI?
- Calif says Quang Luong found Java4Shell with Codex in about one hour and built the first working exploit in about two more hours. The total token cost was under $200. Luong chose which parts of the JDK to examine and supplied exploitation know-how, while Calif's own pipelines and heap tracer helped turn the finding into an exploit.
