VMTech
Discuss a project →

Java4Shell flaw affects Java servers on AVX-512 VBMI processors

Java4Shell flaw affects Java servers on AVX-512 VBMI processors

A newly disclosed Java vulnerability, CVE-2026-114938, dubbed Java4Shell, can allow unauthenticated remote code execution in default deployments of Jira, Jenkins, Keycloak, Confluence, JFrog Artifactory and PingFederate, security research firm Calif says. Oracle and the OpenJDK project released fixes this week for affected builds.

The flaw affects Java 17.0.6 and later in the Java 17 line, plus Java 21, 25 and 27, but only on x86-64 processors that expose AVX-512 VBMI support. Standard Java 8 and Java 11 are not affected, although Java SE 8 Performance Pack build 8u511b33-perf is. Calif assigned a CVSS 4.0 score of 9.2; Oracle assigns 8.1 under CVSS 3.1.

How the Base64 decoder flaw is reached

The vulnerable path is an optimized Java Base64 decoder selected after the JVM compiles frequently used code for performance. It is used on Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids processors, as well as AMD Zen 4 or newer chips. ARM64 systems do not execute this code path.

A malformed Base64 string ending with an extra equals sign can cause the decoder to write 62 or 63 bytes beyond the output buffer. Java rejects the input, but only after the out-of-bounds write has occurred. The written bytes are fixed, meaning an attacker controls where they land rather than their immediate content.

Calif says its technique arranges memory so that the overflow enlarges a neighbouring array, then uses that array for controlled writes and another to read memory in a stage it calls JavaBleed. Exploitation is application-specific: memory layout, timing and network delays can affect whether an attack works. A failed attempt can also crash a JVM.

Exposure depends on runtime and processor

Unauthenticated exposure can arise when an application decodes Base64 data before checking a user session, including HTTP Basic authentication headers, SAML artifacts and CSRF tokens. Calif reported no-login attack paths under default settings in Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. It also reported authenticated paths in Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker.

Independent testing has reproduced the memory corruption without reproducing remote code execution. Upwind reported corruption of a neighbouring object and a subsequent JVM crash on an AWS server using an Intel Ice Lake processor. Blackpoint Cyber crashed a Spring Boot test application with about 28,300 malformed login requests in roughly 20 seconds, and reported successful local JavaBleed reads in 30 runs.

Update runtimes and apply temporary mitigations

Oracle lists fixed releases as 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Amazon Corretto and Azul Zulu have also published updated builds. Red Hat had not released fixes for Red Hat Enterprise Linux 8, 9 and 10 or its OpenJDK 17, 21 and 25 builds at the time of the advisory. Applications shipping their own runtime require an update from their respective vendor.

Where an immediate update is not possible, the JVM flag -XX:-UseBASE64Intrinsics disables the vulnerable accelerated Base64 path. The alternative -XX:UseAVX=2 disables AVX-512 on x86-64, but must not be used on ARM64 because the JVM will fail to start. Upwind reported that both options prevented the overflow in its affected-version tests.

Teams should identify Java services running on compatible processors, patch the runtime, restart Java processes, and rebuild and redeploy container images. Monitoring for malformed Base64 values, bursts of IllegalArgumentException errors from java.util.Base64$Decoder, and unexplained JVM crash logs can support incident triage while remediation is completed.

#javasecurity#vulnerability#remotecodeexecution#patchmanagement
Open analytics
On the site 3 views
min read 4 18.11.2026
Instagram

Java4Shell flaw affects Java servers on AVX-512 VBMI processors

Open the post on Instagram ↗