AI-Found Java4Shell Bug Hits OpenJDK Servers
Security firm Calif disclosed Java4Shell (CVE-2026-114938), a memory-corruption flaw in OpenJDK's Base64 decoder that can allow unauthenticated remote code execution on x86-64 servers with AVX-512 VBMI. Calif says it was found in an hour with OpenAI's Codex. Oracle patched it on Nov. 17.
Security firm Calif on Nov. 17 disclosed Java4Shell (CVE-2026-114938), a memory-corruption flaw in the Base64 decoder of OpenJDK, the most widely used Java runtime. Calif says a researcher found the bug in about an hour using OpenAI's Codex, for less than $200 in AI tokens. Oracle and the OpenJDK project shipped fixes the same day, and the U.S. Cybersecurity and Infrastructure Security Agency (CISA) urged organizations to patch immediately.
Key takeaways
- Java4Shell lets a remote attacker with no credentials overwrite heap memory and, with careful exploitation, leak memory or run code. Calif rates it 9.2 out of 10 under CVSS 4.0; Oracle scores it 8.1 under CVSS 3.1.
- It affects OpenJDK 17.0.6 and newer, plus builds based on it, but only on x86-64 processors with AVX-512 VBMI support. ARM64 machines are not affected.
- Calif researcher Quang Luong says he found the bug in an hour with Codex and built a first working exploit in two more hours.

What the Java4Shell vulnerability is
To decode Base64 text faster, OpenJDK's HotSpot virtual machine uses hand-written machine code that relies on AVX-512 VBMI instructions on x86-64 chips. According to Calif's advisory, that code mishandles a stray padding character at the end of the input and calculates a negative output length.
Calif's example is 64 "A" characters followed by a single "=". OpenJDK allocates a 50-byte result array for that input, but the bug causes a full 64-byte write, sending 62 bytes past the end of the array. Java eventually rejects the input, but neighboring objects may already be corrupted.
Which Java versions and CPUs are affected
Calif says the flaw affects OpenJDK 17.0.6 or newer and distributions built from it, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, Red Hat OpenJDK and Oracle Java SE.
The bug only triggers on CPUs with AVX-512 VBMI. Calif lists Intel Xeon chips from Ice Lake through Granite Rapids and AMD EPYC and Ryzen processors from Zen 4 onward.
In default configurations, Calif demonstrated unauthenticated remote code execution in Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate, and authenticated code execution in Apache Kafka, Apache Solr and Elasticsearch, among others. It also says there is no universal exploit: each application needs its own attack profile.
How AI found the bug
Luong wrote that he pointed Codex at the JIT compiler, intrinsics and cryptography code in OpenJDK. "Most early results Codex brought me were slops," he wrote, before the tool flagged the Base64 issue after about 20 minutes of prompting. "It took our own Quang Luong an hour to discover the vulnerability, and two more hours to develop the first working exploit. The total token cost was less than $200," Calif said.
Calif added that AI agents built most later exploit chains "almost autonomously."
Patches, workarounds and the CISA alert
Oracle included the fix in its November 2026 Critical Security Patch Update, which carries 655 new security patches, 11 of them for Java SE. Oracle credits Quang Luong of Calif.io and Albert Yang. Calif says the OpenJDK project published its own advisory at 1 p.m. Pacific time on Nov. 17.
For systems that cannot update right away, Calif suggests starting Java with -XX:-UseBASE64Intrinsics to turn off the accelerated decoder, or -XX:UseAVX=2 to disable AVX-512. The second flag should only be used on x86-64 hosts, since OpenJDK on ARM will fail to start with it.
CISA issued a notice on the night of Nov. 17 urging organizations to review software inventories, including Java bundled inside third-party applications, and to prioritize internet-facing systems, The Record reported.
Context: a second AI-found bug from Calif
Java4Shell follows PHP2Shell, the PHP flaws Calif and Wiz reported with AI help in October. Calif notes Java powers about 90% of Fortune 500 companies. As of Nov. 17, CyberScoop reported no exploitation in the wild, and the bug was not in CISA's Known Exploited Vulnerabilities catalog. The pattern mirrors other recent cases of AI tools speeding up both sides, such as attackers running agents that rebuilt malware until scanners stopped catching it.
What's next
Calif says it is holding back product-specific exploit chains "until everyone has had a chance to upgrade" and will publish them later. Applications that bundle their own Java runtime will need vendor updates. Oracle's next monthly patch release is scheduled for Dec. 15.
FAQ
Is my Java server vulnerable to Java4Shell?
It may be if it runs OpenJDK 17.0.6 or newer, or a build based on it, on an x86-64 CPU with AVX-512 VBMI. ARM64 servers are not affected. Updating to the November patched release is the fix.
Is Java4Shell being exploited?
As of Nov. 17, no exploitation in the wild had been reported, according to CyberScoop, and CISA had not added it to its exploited-vulnerabilities list.
Did AI find Java4Shell on its own?
No. Calif researcher Quang Luong directed Codex and verified its findings. Calif says AI did much of the work, but humans supplied the context.
References
- Java4Shell: Write once, RCE everywhere — Calif (Nov. 17, 2026)
- Oracle Critical Security Patch Update Advisory - November 2026 — Oracle (Nov. 17, 2026)
- CISA warns of 'Java4Shell,' an AI-found Java bug touching most of the Fortune 500 — The Record (Nov. 18, 2026)
Editor responsible for AI Newsway. Writes about AI, developer tools, cloud and productivity technology.
Comments 0
Comments are currently disabled.