Security researchers from Calif have disclosed a critical vulnerability dubbed Java4Shell (CVE-2026-114938), affecting Java's optimised Base64 decoder implementation. According to Calif's testing, the vulnerability may allow unauthenticated attackers to achieve remote code execution (RCE) against multiple enterprise applications including Atlassian Jira, Atlassian Confluence, Jenkins, Keycloak, JFrog Artifactory, and PingFederate under default configurations.
The vulnerability exists in Java versions 17.0.6 and later and only affects systems using specific x86-64 processors supporting the AVX-512 VBMI instruction set. Researchers demonstrated that malformed Base64-encoded input processed before authentication can trigger memory corruption, potentially leading to arbitrary code execution.
Oracle and the OpenJDK project released fixes on 17 November 2026. While no confirmed in-the-wild exploitation has been reported, exploitation attempts have been observed and the vulnerability impacts widely deployed enterprise software and identity management platforms, significantly increasing the risk of rapid weaponisation.
Key Findings
- Critical Java vulnerability enabling pre-authentication remote code execution.
- Tracked as CVE-2026-114938 and commonly referred to as Java4Shell. Calif scores it 9.2 (CVSS v4.0); Oracle scores it 8.1 (CVSS v3.1).
- Impacts Java's optimized Base64 decoding functionality.
- Requires no authentication against several affected enterprise applications.
- Affects only x86-64 systems supporting AVX-512 VBMI instructions. ARM64 systems and standard Java 8 and 11 builds are not known to be affected.
- Calif reports successfully demonstrating exploitation against Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. These results come from Calif's own testing and are not vendor-confirmed.
- No confirmed exploitation observed by the Canadian Centre for Cyber Security or inclusion in CISA's Known Exploited Vulnerabilities (KEV) catalogue. GreyNoise has reported exploitation attempts.
Technical Analysis
The vulnerability affects Java's accelerated Base64 decoding implementation used on processors supporting AVX-512 VBMI instructions. When a malformed Base64 string ending with an extra "=" character is processed, the decoder writes data beyond the allocated memory boundary before validation occurs.
Many enterprise applications perform Base64 decoding before user authentication occurs, including processing:
- HTTP Basic Authentication headers
- SAML artefacts
- Other authentication data and file uploads
By manipulating memory layout and leveraging a memory disclosure technique researchers named JavaBleed, attackers can read sensitive data from memory and progress from memory corruption to code execution within the Java Virtual Machine (JVM).
Unlike many recent Java vulnerabilities, exploitation is highly environment-specific and depends on application memory layout, runtime conditions, and processor architecture. Nevertheless, the demonstrations reported against major enterprise products indicate a realistic exploitation pathway.
Impacted Products and Technologies
Reported Pre-Authentication Exposure
Calif reports that the following products were vulnerable under default configurations. This has not been confirmed by all of the product vendors.
|
Product |
Exploitation Requirement |
|
Keycloak |
No Authentication |
|
Atlassian Jira |
No Authentication |
|
Atlassian Confluence |
No Authentication |
|
JFrog Artifactory |
No Authentication |
|
Jenkins |
No Authentication |
|
PingFederate |
No Authentication |
Additional Products Requiring Authentication
Calif also identified potential exploitation paths requiring authenticated access against Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker.
Affected Java Versions
|
Platform |
Vulnerable Versions |
Fixed Version |
|
Oracle Java SE 17 |
17.0.6 - 17.0.21.0.3 |
17.0.21.1 |
|
Oracle Java SE 21 |
Up to 21.0.13.0.3 |
21.0.13.1 |
|
Oracle Java SE 25 |
Up to 25.0.5.0.3 |
25.0.5.1 |
|
Oracle Java SE 27 |
Up to 27.0.1.0.3 |
27.0.1.1 |
|
Eclipse Temurin |
Multiple affected releases |
Vendor fixes being released |
|
Amazon Corretto |
Multiple affected releases |
Vendor fixes available |
|
Azul Zulu |
Multiple affected releases |
Vendor fixes available |
|
Red Hat OpenJDK |
Affected |
Fixes pending |
Other OpenJDK distributions are also affected. Vendor status is as reported on 18 November 2026 and is changing quickly.
Threat Assessment
Several factors increase the likelihood of future exploitation:
- Internet-accessible attack surface.
- Impacts common identity and collaboration platforms.
- Pre-authentication attack vector.
- Public disclosure and technical details available.
- Vendor advisories and widespread security community attention.
Potential Impact. Successful exploitation could lead to:
- Remote code execution on application servers.
- Identity platform compromise.
- Credential theft and token harvesting.
- SAML federation abuse.
- Lateral movement within enterprise environments.
- Persistence deployment and malware installation.
- Full takeover of vulnerable Java applications.
Detection Opportunities
No vendor-confirmed indicators of compromise have been published. The following are general hunting leads based on how the vulnerability behaves, and should not be treated as confirmed indicators.
Application Indicators
- Excessive malformed Base64 strings, particularly those ending with unexpected "=" padding.
- Unusual authentication token processing errors.
JVM Indicators
- Repeated java.lang.IllegalArgumentException exceptions originating from java.util.Base64$Decoder.
- Unexpected JVM crashes and creation of hs_err_pid*.log files.
- Unplanned application restarts.
Mitigations
Priority 1 - Patch Immediately
Upgrade all affected Java runtimes to vendor-fixed releases:
- Oracle Java 17.0.21.1+, 21.0.13.1+, 25.0.5.1+ or 27.0.1.1+
- Latest patched builds from your Java vendor (for example Amazon Corretto, Azul Zulu, Eclipse Temurin)
Additionally:
- Restart Java services after upgrading.
- Rebuild and redeploy affected containers.
- Verify bundled JRE versions inside enterprise products.
Temporary Workarounds
Where patching cannot be performed immediately, Calif and Red Hat recommend the following JVM options.
Disable Vulnerable Base64 Intrinsics (preferred). This disables the vulnerable accelerated decoder while retaining other AVX-512 optimizations.
-XX:-UseBASE64Intrinsics
Alternative Mitigation. This disables AVX-512 usage entirely. Apply on x86-64 systems only; Java on ARM64 will fail to start with this option.
-XX:UseAVX=2
References
- Oracle Critical Security Patch Update, November 2026: https://www.oracle.com/security-alerts/cspunov2026.html
- Red Hat security bulletin RHSB-2026-018: https://access.redhat.com/security/vulnerabilities/RHSB-2026-018
- Calif research: https://calif.io/java4shell/
If you are worried about any of the threats outlined in this bulletin or need help in determining what steps you should take to protect yourself from the most material threats facing your organisation, please contact your account manager, or alternatively get in touch to find out how you can protect your organisation.
