Live wire

Java4Shell Flaw Enables Pre-Auth Code Execution on AVX-512 Java Servers

Researchers say Jira, Jenkins, Keycloak and others are exposed on certain x86 chips; Oracle has patched, but exploits are unreliable and not seen in attacks.

Researchers have disclosed a flaw they call Java4Shell, tracked as CVE-2026-114938, in the accelerated Base64 decoder that Java uses on x86-64 processors supporting a feature called AVX-512 VBMI. They say it allows remote code execution without a login. A malformed string ending in an extra equals sign makes the decoder write 62 or 63 bytes past its output buffer, and Java rejects the input only after the write. Servers often decode Base64 from HTTP Basic authentication headers, SAML artifacts and CSRF tokens before checking authentication, which is the attack path.

Who is exposed

The researchers list Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate as exposed without a login by default, and Apache Kafka, Solr, Elasticsearch, Gerrit and Spinnaker with a login; they say the list is incomplete. Affected Java builds include 17.0.6 and later and Java 21, 25 and 27, plus some performance and GraalVM builds. Standard Java 8 and 11 and ARM64 chips are not affected, and exposure depends on the server's processor, so the same container image can be vulnerable on one host and not on another.

Exploitation and fixes

The researchers are withholding their attack code. Other labs reproduced crashes and a memory leak but not code execution, Canada's cyber centre knew of no attacks, and the flaw was not in the US known-exploited list when checked. Exploits are not reliable across targets because each needs its own memory layout and timing, but a failed attempt usually crashes Java and attackers can often retry. Severity scores range from 8.1 to 9.8 depending on the scorer.

Oracle has patched with versions 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, and Amazon Corretto and Azul Zulu have fixed builds, but Red Hat had no fix yet and container images must be rebuilt once fixed ones ship. Interim mitigations are a Java option that disables only the vulnerable Base64 path, or one that disables AVX-512 entirely on x86-64. Defenders should look for long Base64 tokens ending in an equals sign whose length is not a multiple of four, bursts of decoder exceptions and unexplained crash logs; none of these proves compromise. The report mentions no India or Southeast Asia link.

Topics