What Calif disclosed on 17 November
Security firm Calif disclosed Java4Shell, tracked as CVE-2026-114938, on 17 November with a CVSS 4.0 score of 9.2. It is a heap out-of-bounds write in the x86-64 Base64 decoder of OpenJDK, present from 17.0.6 onward, so it sits in Temurin, Corretto, Zulu, Oracle Java SE and the other builds of it. Any service that decodes Base64 from outside input can reach it.
Calif says it showed pre-authentication code execution in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate in default setups. It is holding back those exploit chains until people can upgrade, and the public proof of concept only shows a write 62 bytes past the buffer. Neither Calif nor JFrog reports exploitation in the wild.
The hardware decides who is exposed
The flaw only fires on x86-64 chips with AVX-512 VBMI: Intel Xeon from Ice Lake to Granite Rapids, and AMD EPYC and Ryzen from Zen 4. ARM64 servers are not affected. That turns this into a fleet inventory question rather than a version question, because a Java 21 service on an ARM instance is fine while the same container on a recent Xeon is not.
The cost is the part to remember. Calif says an engineer using Codex found the bug in about an hour, built a first working exploit in about two more and spent under 200 dollars in tokens. We read that as a new patch clock: a bug this cheap to find will be found by others too, so the held-back chains buy you days, not months.
What to do before the exploit chains ship
Check each Linux host for avx512vbmi in /proc/cpuinfo, list the Java services on those that have it and move them to the fixed builds JFrog lists: 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Start with identity, CI and wiki servers, because those are the products Calif named.
Where you cannot patch today, either JVM flag blocks the path: -XX:-UseBASE64Intrinsics or -XX:UseAVX=2. Do not set UseAVX on ARM, which then refuses to start. Under NIS2 and DORA, an unpatched critical flaw on an identity server with a published fix is the gap an auditor asks about first.
Read next: When Email Security Becomes a Jurisdiction Question | Beacon's Breach Falls Outside Every Safety Net



