← All security news
SecurityVulnerabilityCRITICAL

Java4Shell: a critical OpenJDK flaw in Base64 decoding can let attackers run code on Java servers with modern x86 CPUs; update Java now

· 2 min read

Calif disclosed CVE-2026-114938 on 17 November: a heap overflow in the JVM's AVX-512 Base64 decoder, rated 9.2. It says it ran code with no login in Jenkins, Jira, Confluence and Keycloak. Oracle shipped new Java builds the same day; no attacks are reported yet.

OpenJDK / Java

Security firm Calif disclosed Java4Shell (CVE-2026-114938) on 17 November 2026, rated 9.2 (critical) under CVSS 4.0. According to Calif's write-up, the bug sits in a hand-written AVX-512 routine that the HotSpot JIT compiler uses to speed up Base64 decoding. For certain malformed input it writes 64 bytes about 62 bytes past the end of the output array; Java then rejects the input with an error, but the memory is already corrupted. Calif says that can leak heap memory (keys, tokens, personal data) or lead to remote code execution.

Who is affected, per Calif: OpenJDK 17.0.6 and newer, and builds based on it such as Eclipse Temurin, Amazon Corretto, Microsoft Build of OpenJDK, Azul Zulu, Red Hat OpenJDK, Oracle Java SE and GraalVM. The bug only fires on x86-64 CPUs with AVX-512 VBMI — Intel Xeon from Ice Lake on and AMD Zen 4 or newer, which covers many current cloud servers. ARM64 is not affected. Other write-ups say only Java 17 is confirmed and Java 21, 25 and 27 are still unclear, so treat every recent Java on such hardware as at risk.

What Calif says it showed: code execution with no login in Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate, and after login in Kafka, Solr, Elasticsearch, Gerrit and Spinnaker, because ordinary features such as sign-in and file upload decode Base64. It calls exploitation complex (JIT warm-up, heap grooming, timing) and is holding back the app-specific exploit chains so people can patch. A client-side variant also exists: a Java program that opens a TLS connection to a malicious server can be hit.

Patches: Oracle's November Critical Patch Update, also out on 17 November, has 11 Java SE fixes, all exploitable over the network without credentials. ThreatDefence lists the new builds as 8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Calif says OpenJDK and Oracle released fixes that day, but other reports note Oracle has not yet tied a specific fix to this CVE, and builds from Temurin, Corretto, Zulu and others ship on their own schedules. No attacks in the wild are reported so far, and the CVE is not in CISA's KEV list.

More news