Security firm Calif disclosed Java4Shell on Nov. 17, a critical memory-corruption flaw in OpenJDK that its researcher Quang Luong found in about an hour by auditing the Java runtime with OpenAI's Codex. Calif says the hunt cost under $200 in computing tokens, and the first working exploit took about two more hours.
Tracked as CVE-2026-114938, the bug sits in OpenJDK's Base64 decoder intrinsic, a speed-optimized routine for x86-64 processors that support AVX-512 VBMI instructions. Feeding it 64 letter A's followed by an equals sign makes the decoder write 64 bytes into a 50-byte array, pushing 62 bytes past the end before Java throws an error. By then the write has already happened.
Calif says that overwrite can be chained into a Heartbleed-style memory leak it calls JavaBleed, or into remote code execution. In its initial tests, Calif achieved unauthenticated code execution against default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. It also showed authenticated execution in Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker, and calls both lists non-exhaustive.
Key facts
- 01Calif researcher Quang Luong found Java4Shell (CVE-2026-114938) in about an hour using OpenAI Codex, for under $200 in tokens.
- 02The first working exploit took about two more hours; Calif says AI agents produced most of its exploit chains.
- 03Oracle shipped fixes in its November 2026 Critical Patch Update on Nov. 17, the same day as Calif's 1 p.m. PT disclosure.
- 04Calif rates the flaw 9.2 on CVSS 4.0; Oracle's advisory scores it 8.1 on CVSS 3.1 with high attack complexity.
- 05Only x86-64 servers with AVX-512 VBMI are exposed; ARM64 is not affected, and -XX:-UseBASE64Intrinsics blocks the overflow.
Oracle shipped fixes the same day in its November 2026 Critical Patch Update, which resolves 11 Java SE vulnerabilities. OpenJDK published its own advisory listing Java 17, 21, 25 and 27 as affected. Calif rates the flaw 9.2 on CVSS 4.0, while Oracle's advisory scores it 8.1 on CVSS 3.1, citing remote, unauthenticated access with high attack complexity.
The exposure is narrower than every Java install. Calif says OpenJDK 17.0.6 and newer are affected on Intel Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids chips and on AMD Zen 4 or newer. ARM64 servers are not affected. Downstream builds including Amazon Corretto, Eclipse Temurin, the Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK inherit the bug and need their own vendor releases.
Those vendor builds were still catching up on disclosure day. Endor Labs said the fix had not yet landed in the public OpenJDK 17, 21 and 25 update repositories as of Nov. 17. For systems that cannot be updated immediately, Calif recommends launching the JVM with -XX:-UseBASE64Intrinsics, or -XX:UseAVX=2 on x86-64 only, since OpenJDK on ARM fails to start with that flag.
Calif says there is no universal exploit. Each product needs its own chain, and the firm is withholding product-specific exploits until users have had time to upgrade. VulnCheck said crashing a vulnerable JVM is easy once an entry point is found, but full code execution requires defeating heap layout and address randomization per target, and it does not expect the CVE to be easily or widely exploitable.
Cisco Talos said it has not seen exploitation in the wild but expects probing to pick up after public disclosure. The US Cybersecurity and Infrastructure Security Agency called for immediate patching, prioritizing internet-facing systems, and advised organizations to hunt for Java runtimes embedded in third-party software, containers and appliances.
Java4Shell is Calif's second major AI-assisted vulnerability find, following a PHP flaw it called php2shell last month. Calif describes its approach as a human researcher steering AI coding agents through the search and the exploit work, with the agents producing most of the exploit chains for the affected products.
Working on something we should cover, or seeing a story we missed? Send leads, documents, or feedback to hello@aichatdaily.com. For sensitive tips, see our secure tips page for Signal and PGP options.
Spotted an error? Email hello@aichatdaily.com with the URL and the issue, or read our full corrections policy.




