Java4Shell, a heap out-of-bounds vulnerability hiding in OpenJDK's Base64 decoder, was publicly disclosed on November 17, tracked as CVE-2026-114938. Security firm Calif says it lets an attacker run code remotely without logging in; Oracle released fixed builds the same day, and the U.S. Cybersecurity and Infrastructure Security Agency (CISA) issued an urgent patching warning. Notably, AI helped find the flaw: a researcher auditing code with AI located the problem in about an hour and built a working exploit two hours later.
| Affected | Not affected | |
|---|---|---|
| Java versions | Unpatched OpenJDK 17.0.6+ (21/25/27) | Standard Java 8, 11 |
| Processors | x86-64 with AVX-512 VBMI (Xeons after Ice Lake, AMD after Zen 4) | ARM64, older Xeons, AMD before Zen 4 |
| Trigger | Attacker input reaching the Base64 decoder | JVMs with hardware-accelerated decoding off |
The severity scores disagree — size up the risk first
Assessments of how dangerous the flaw is do not fully agree. The discoverers scored it 9.2 under CVSS 4.0, a critical rating; Oracle's own record gives it 8.1 under CVSS 3.1 and marks it difficult to exploit. The disagreement is about the path from an out-of-bounds heap write to actual remote code execution, which takes several more steps including heap grooming, with no universal method. Calif demonstrated unauthenticated remote code execution against default installations of Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate; Wiz's Atlas AI system produced a proof of concept within two hours and confirmed remote execution on Jira, Confluence, and Jenkins. As of November 17, there was no public evidence of exploitation in the wild, and the flaw had not entered CISA's Known Exploited Vulnerabilities catalog. The risk is real; there is no need to panic.
Three things to do today
- Upgrade the Java runtime: Oracle has released fixed builds 17.0.21.1, 21.0.13.1, and 25.0.5.1, and upgrading is the only complete fix.
- If you cannot upgrade yet, turn off hardware-accelerated Base64 decoding: adding the -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 JVM flag closes the trigger path.
- Take stock of your exposure: public-facing Java applications such as Jenkins and Confluence come first. The flaw had already leaked before the patch arrived: South Korea's National Cyber Security Center told public institutions to inspect their Java runtimes on November 16. With supply-chain poisoning and open-source tool risks appearing in quick succession, patch windows for the Java ecosystem are getting shorter.
Java4Shell is worth remembering for more than the vulnerability itself: a researcher located the problem in about an hour and built an exploit in two, for under $200 in token costs; Wiz's AI system produced a proof of concept in two hours as well. AI now finds vulnerabilities as fast as humans can patch them. For companies, patching faster than attackers is already a hard requirement.