A Java flaw called Java4Shell can let attackers without an account run their own code on Jira, Jenkins, Keycloak, and three other widely used applications, says Calif, the security research firm that disclosed it this week.
The flaw is present in Java 17.0.6 and later, and the vulnerable code runs only on x86-64 Intel and AMD chips that support the AVX-512 VBMI feature. Tracked as CVE-2026-114938, the fix was released today by Oracle and the OpenJDK project, whose open-source code underpins Java builds from many vendors.
Servers often decode Base64-encoded data, such as HTTP Basic login headers, SAML artifacts, and CSRF tokens, before checking whether a user is logged in. That is how an attacker without an account can exploit the flaw. The flaw is in a faster version of Java's Base64 decoder that runs on chips with AVX-512 VBMI.
A malformed string that ends with an extra = makes this decoder write 62 or 63 bytes past the end of its output. Java rejects the string, but only after the write. The bytes written past the end are fixed, so an attacker controls only where they land.
Affected Applications and Exploitation
The attacks worked without a login under the default settings of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate, and with a login on Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker.
The researchers get past the fixed bytes by arranging the server's memory so that the overflow expands a neighboring array. They then use that array to write bytes of their choosing and a second array to read back from memory, a step they call JavaBleed. From there, the researchers say, the attack reaches the parts of Java that run code.
Vendor Scores and Patch Status
Oracle scores the flaw 8.1 out of 10 under CVSS 3.1. Red Hat rates it as requiring no login, with a preliminary score of 9.8 out of 10. Amazon scores it 8.8 out of 10.
For Oracle Java, the fixed builds are the new .1 releases released this week. Amazon Corretto 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4 are fixed. Azul Zulu November updates also address the issue. Red Hat has not yet released fixes for RHEL 8, 9 and 10 or its OpenJDK builds.
Mitigations
If you cannot update yet, start the JVM with one of these flags: -XX:-UseBASE64Intrinsics turns off only the faster Base64 code. -XX:UseAVX=2 turns off AVX-512 entirely.


