The Short Answer
Java4Shell (CVE-2026-114938) is an OpenJDK Base64 flaw a researcher found with an AI coding agent in about an hour, months after it was first reported. The lesson is that discovery is now cheap and patch speed decides exposure. On ibl.ai you own all the code and the data, so the patch schedule is yours.
Java4Shell was disclosed and fixed on November 17, 2026. Oracle and the OpenJDK project released patches that day, per Calif's disclosure, the security research firm that reported it.
The vulnerable code runs only on x86-64 processors with AVX-512 VBMI: Intel Xeon from Ice Lake onward and AMD Zen 4 or newer.
What is Java4Shell (CVE-2026-114938)?
Java4Shell (CVE-2026-114938) is an out-of-bounds heap write in the hand-written assembly OpenJDK uses to decode Base64 quickly. A malformed string, as short as 64 "A" characters and one "=", makes the routine write 62 bytes past a 50-byte array before Java rejects the input.
Calif reports remote code execution in default configurations of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate without logging in, and in Kafka, Solr, Elasticsearch, Gerrit and Spinnaker with a login, per its write-up.
The reason a login is often not needed: servers decode Base64 in HTTP Basic headers, SAML artifacts and CSRF tokens before they check who you are, as The Hacker News explains.
Which Java versions and CPUs does Java4Shell affect?
Java4Shell affects OpenJDK 17.0.6 and newer, and the builds made from it, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, Red Hat OpenJDK and Oracle Java SE, according to Calif's affected-products list.
The processor must be x86-64 with AVX-512 VBMI: Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, or AMD Zen 4 and newer. ARM64 servers are not affected.
| Who scored it | Score | Scale |
|---|---|---|
| Calif (the researchers) | 9.2 | CVSS 4.0 |
| Red Hat (preliminary) | 9.8 | CVSS |
| Amazon | 8.8 | CVSS |
| Oracle | 8.1 | CVSS 3.1 |
Sources: Calif and The Hacker News. The "9.2" in most headlines is the researchers' CVSS 4.0 score; vendor scores differ, so read your own vendor's advisory.
Did AI discover Java4Shell?
AI did the search and a human directed it. Calif's Quang Luong asked OpenAI's Codex on October 24, 2026 to audit Netty and the JVM, focusing on x64 intrinsics. Codex found the bug within an hour.
The first working exploit took two more hours at under $200 in tokens, per Calif.
Calif says most of Codex's early findings were unusable and credits the result to "the centaur hacker, part human, part AI." It is not a story of an autonomous system finding bugs on its own, and it is not the first time this has happened.
In October, Calif, OpenAI and Wiz disclosed PHP2Shell, two remote PHP flaws (CVE-2026-109618 and CVE-2026-109619) patched in PHP's October 21, 2026 release. Two remote code execution bugs in core runtimes within two months, both found with AI help.
Why was Java4Shell patched only after an exploit was demonstrated?
Java4Shell was patched only after exploits were shown because the bug sat in public for months without anyone proving its impact. A user hit the crash on June 9, 2026 and opened an Adoptium issue, and on September 8 posted a reproduction, per Calif's timeline.
The next day an OpenJDK contributor proposed a fix. That pull request was closed without being merged. Calif reported the bug to Oracle with a working exploit on October 24, and the fix shipped on November 17, 24 days later.
Calif notes PHP2Shell followed the same pattern: reported, then fixed only once someone demonstrated it could be exploited. That is the real edge of this story. The bottleneck is no longer finding the bug. It is acting on a report that already exists.
What should a security team do about Java4Shell right now?
A security team should patch Java first, then use the published mitigations where a patch has to wait. Calif lists two JVM flags: -XX:-UseBASE64Intrinsics, which turns off the accelerated decoder, or -XX:UseAVX=2, which turns off AVX-512 and affects other operations.
Apply either flag only on x86-64 hosts; OpenJDK on ARM does not recognise them and fails to start, per Calif. As of November 2026, Canada's Cyber Centre said it was not aware of attacks exploiting the flaw.
Then list every system that runs Java on an affected CPU, including the ones you do not operate. For a hosted product, the honest answer to "are we patched?" is the vendor's statement, on the vendor's timeline.
How does owning your AI stack change patch speed when AI finds bugs this fast?
Owning your AI stack changes patch speed because the team that reads the advisory is the team that can deploy the fix. When you hold the source and run it in your own infrastructure, you can check the runtime, apply a flag and redeploy the same afternoon.
ibl.ai is the agentic AI platform where you own all the code and the data. Organizations deploy it in their own cloud, on-premise, GovCloud or air-gapped, which puts the patch and the audit inside their own change process rather than a vendor's queue.
The same tools that found Java4Shell can work for defenders. Calif calls it "vibe-uncoding": using AI to find code a system does not need and remove it.
Running those agents against your own repositories is safer inside a sandbox you control; see how an open-source AI pentester runs in a sandbox you own.
For the earlier signal, see AI just found a 23-year-old Linux kernel vulnerability, and for the identity side of agent security, AI agents outrun static credentials.
ibl.ai is family-owned and operated from New York, NY, and our engineers work alongside your team, so the people applying the patch are yours.