A critical security vulnerability dubbed Java4Shell has raised widespread concern across global enterprise software and server infrastructure, exposing at least six major platforms to potential cyberattacks. Tracked as CVE-2026-114938, the flaw allows cybercriminals to execute arbitrary remote code on vulnerable servers without needing a user account or login credentials. Affected platforms include Atlassian Jira, Jenkins, Keycloak, Confluence, JFrog Artifactory, and PingFederate. Security researchers have assigned the vulnerability a severe rating of 9.2 out of 10 on the CVSS 4.0 scoring scale.
How the Flaw Exploits Memory Without Authentication
According to security research firm Calif, the vulnerability resides in a high-speed version of Java’s Base64 decoder that activates on processors supporting AVX-512 VBMI technology. The issue occurs when a server decodes malformed Base64 data, which can reach the system through HTTP Basic Authentication headers, SAML artifacts, or CSRF tokens. Because servers routinely decode incoming data before verifying a user’s identity, attackers can send specially crafted Base64 inputs to trigger the flaw without logging in.
Researchers explained that appending extra equals signs to the end of a malformed input causes the decoder to write 62 or 63 bytes beyond its designated output buffer. Although Java eventually rejects the invalid input, unauthorized modifications have already occurred in the system memory. Initially thought to cause only server crashes, researchers developed a technique named JavaBleed that manipulates adjacent memory areas to read sensitive data and reach code execution components. Because each software application requires a specific memory layout and timing, a single exploit does not work universally across all platforms.
Lab Testing and Affected Java Versions
Independent security laboratories have confirmed the real-world risks of the vulnerability. Security firm Upwind verified memory corruption on an AWS server powered by an Intel Ice Lake processor, where an adjacent memory object was altered and the Java process crashed. Similarly, Blackpoint Cyber’s Adversary Pursuit Group crashed a Spring Boot application in roughly 20 seconds by sending 28,300 invalid login requests without authenticating. The team also extracted confidential data from local memory across all 30 test attempts using the JavaBleed method, though full remote code execution was not independently demonstrated. Canada’s Cyber Centre noted there are currently no reports of active exploitation in the wild.
The flaw affects Java 17.0.6 and later releases, alongside Java 21, 25, and 27, as well as certain GraalVM editions and a specialized build of Java SE 8 Performance Pack. Standard Java 8 and Java 11 versions are unaffected. Hardware exposure is limited to modern x86-64 processors with AVX-512 VBMI support, including Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids, and Granite Rapids, as well as AMD Zen 4 and newer chips. ARM64 processors do not trigger the vulnerable code, meaning identical container images carry different risk levels depending on the underlying server hardware.
Security Updates and Temporary Mitigations
Oracle, OpenJDK, Amazon Corretto, and Azul have released patches to address the vulnerability. Oracle has issued fixed versions including 17.0.21.1 for Java 17, 21.0.13.1 for Java 21, 25.0.5.1 for Java 25, and 27.0.1.1 for Java 27. Updates for Red Hat Enterprise Linux 8, 9, and 10, along with Red Hat’s OpenJDK builds, remain in preparation. Organizations using software that bundles its own Java Runtime Environment must wait for patches from their respective vendors.
For enterprises unable to apply patches immediately, security experts recommend disabling the fast Base64 decoding feature by launching the Java Virtual Machine with the -XX:-UseBASE64Intrinsics flag, or turning off AVX-512 on x86-64 servers using the -XX:UseAVX=2 flag. Administrators are also advised to monitor systems for suspicious Base64 tokens, IllegalArgumentException errors, unexpected hs_err_pid crash logs, and repeated server restarts. Researchers noted that a malformed input triggering the bug first appeared publicly in an unmerged OpenJDK repository pull request on September 9 before closing in early November, making rapid patching essential for affected enterprises.
