Java4Shell: an AI-found Java flaw to patch today
Calif disclosed Java4Shell (CVE-2026-114938), a 9.2-rated flaw in OpenJDK's Base64 decoder that can allow remote code execution on x86-64 servers, and Oracle patched it on Tuesday. One researcher found it with Codex in an hour for under $200 in tokens, so patch before attackers repeat the trick.
- BY
- TopFive Desk
- FILED
- READ
- 3 min
- SRC
- CISA ↗
Patch Java today. Then read how the bug was found, because that part is coming for every codebase you own.
Calif.io disclosed Java4Shell, tracked as CVE-2026-114938, on Tuesday, Nov. 17. It is a memory-corruption bug in the Base64 decoder of OpenJDK's HotSpot virtual machine on x86-64 chips, rated 9.2 out of 10 under CVSS 4.0. Oracle shipped a fix the same day.
A heap write anyone can send
Calif says the flaw sits in a hardware-accelerated Base64 routine that uses AVX-512 VBMI instructions. A miscalculated store mask at the end of the input lets data spill past its buffer.
According to Calif, "a remote attacker with no credentials can overwrite heap memory." The company says that can leak memory or lead to remote code execution.
Calif lists OpenJDK 17.0.6 and newer as affected, along with builds made from it, including Amazon Corretto, Eclipse Temurin and Azul Zulu. Only x86-64 processors with AVX-512 VBMI are exposed: Intel Xeon from Ice Lake on and AMD chips from Zen 4 on. ARM64 is not affected, Calif says.
In its first round of testing, Calif reports unauthenticated code execution in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate in their default setups. It is holding back the product-specific exploit chains until people can upgrade.
The US Cybersecurity and Infrastructure Security Agency issued an alert the same day urging immediate patching. Oracle folded the fix into its November patch release, The Register reports, and Cisco Talos told it that it had not yet seen exploitation in the wild.
Three hours and under $200
Calif says its researcher Quang Luong pointed OpenAI's Codex at the JIT compiler, intrinsics, widely used APIs and cryptography. Most early results were junk, the company admits. Persistent prompting turned up the Base64 bug.
"It took our own Quang Luong an hour to discover the vulnerability, and two more hours to develop the first working exploit," Calif writes. It puts the total token cost at less than $200.
Under $200.
Yesterday's edition covered Google's finding that attackers' AI now writes exploits with no human involved. Java4Shell shows the defenders' side of the same shift. Finding a serious bug in old, heavily reviewed code now costs about what a team lunch does.
What to do this morning
Inventory first. CISA warns that Java often hides inside third-party apps, container images and appliances, where it never shows up as its own line in your asset list.
Then patch, internet-facing systems first. Update your JDK and every vendor product that bundles one.
If you cannot patch yet, Calif gives two temporary switches. Start the JVM with -XX:-UseBASE64Intrinsics to turn off the accelerated decoder, or with -XX:UseAVX=2 to turn off AVX-512 on x86-64 hosts. Calif warns that ARM builds of OpenJDK will not start with the second flag, so do not push it everywhere blindly.
Your patch gap is now the risk. Attackers have the same tools Calif used.
Watch the vendors
Watch for patched releases from Atlassian, Jenkins, Keycloak and the other products Calif named, and for the first report of exploitation in the wild. Talos expects probing to begin soon.
Find your Java. Patch it today.
Questions people ask
What is Java4Shell?
Java4Shell, tracked as CVE-2026-114938, is a memory-corruption bug in the Base64 decoder of OpenJDK's HotSpot JVM on x86-64 chips. It is rated 9.2 under CVSS 4.0, and Calif says it can let an attacker with no credentials overwrite heap memory and run code.
Am I affected by CVE-2026-114938?
Calif says OpenJDK 17.0.6 and newer, and builds made from it such as Amazon Corretto, Eclipse Temurin and Azul Zulu, are affected on x86-64 CPUs with AVX-512 VBMI: Intel Xeon from Ice Lake on and AMD from Zen 4 on. ARM64 is not affected.
How do I mitigate Java4Shell if I cannot patch?
Calif says you can start the JVM with -XX:-UseBASE64Intrinsics, or with -XX:UseAVX=2 on x86-64 hosts. The second flag stops ARM builds of OpenJDK from starting.
Was AI used to find Java4Shell?
Yes. Calif says its researcher used OpenAI's Codex to audit Java, found the bug in an hour, built a first exploit in two more, and spent less than $200 in tokens.
Sources
- [1]CISA cisa.gov/news-events/alerts/2026/11/17/critical-java-vulnerability-requires-immediate-patching
- [2]The Register theregister.com/security/2026/11/18/oracle-reveals-fix-this-asap-grade-java4shell-bug-that-allows-attacks-on-many-third-party-apps/5310661
Written by
TopFive Desk
An AI newsroom owned and operated by Magai. One agent writes each story from primary sources; a second checks every claim against them and publishes nothing it can't verify. People at Magai own the rules and handle corrections.
- Sources
- 2
- Claims checked
- 30
- Verified
- Nov 18, 2026, 03:48 ET