What Is the Java4Shell Vulnerability?
A critical Java4Shell vulnerability tracked as CVE-2026-114938 can enable attackers to execute code remotely on widely used enterprise applications without authentication, according to security research firm Calif, which disclosed the flaw this week. The vulnerability affects popular platforms including Jira, Jenkins, Keycloak, Confluence, JFrog Artifactory, and PingFederate under default settings.
The flaw is present in Java 17.0.6 and later, and the vulnerable code runs only on x86-64 Intel and AMD chips supporting the AVX-512 VBMI feature. Oracle and the OpenJDK project released fixes this week, though some vendors are still preparing patches.
Source: The Hacker News – Java4Shell CVE-2026-114938 Enables Pre-Auth RCE
What Happened With CVE-2026-114938?
Calif disclosed the Java4Shell vulnerability this week, revealing that attackers without an account could potentially run their own code on affected systems. The researchers rated the flaw 9.2 out of 10 under CVSS 4.0, whilst Oracle scored it 8.1 and Red Hat assigned a preliminary score of 9.8.
According to the report, the following applications were vulnerable to pre-authentication attacks under default settings:
- Keycloak
- Atlassian Jira
- Atlassian Confluence
- JFrog Artifactory
- Jenkins
- PingFederate
Additional applications including Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker were vulnerable with authentication. The researchers note their lists are incomplete.
Canada’s Cyber Centre stated it was not aware of any attacks exploiting the flaw at the time of disclosure. The flaw was not in CISA’s Known Exploited Vulnerabilities (KEV) catalog when checked by The Hacker News.
How Does the Java4Shell Attack Work?
The vulnerability exists in a faster version of Java’s Base64 decoder that runs on chips with AVX-512 VBMI. Java switches to this optimised decoder after compiling it for speed, which occurs for frequently executed code.
According to the technical analysis, a malformed string ending with an extra = character causes the decoder to write 62 or 63 bytes past the end of its output buffer. Java rejects the string, but only after the write has occurred.
Why Pre-Authentication Exploitation Is Possible
Servers commonly decode Base64-encoded data—including HTTP Basic login headers, SAML artifacts, and CSRF tokens—before checking whether a user is logged in. This processing order allows attackers without credentials to trigger the vulnerability.
The JavaBleed Technique
The researchers bypass the limitation of fixed bytes by arranging server memory so the overflow expands a neighbouring array. They then use:
- The expanded array to write bytes of their choosing
- A second array to read back from memory (dubbed “JavaBleed”)
- These primitives to reach Java’s code execution components
Calif notes there is no single exploit that works everywhere—each target requires its own memory layout and timing, with some attacks sensitive to network delays.
Independent Verification and Business Impact
Multiple security firms have attempted to reproduce the findings with varying results:
- Upwind reproduced memory corruption on an AWS server with an Intel Ice Lake chip, causing Java to crash
- Blackpoint Cyber’s Adversary Pursuit Group crashed a test Spring Boot application by sending approximately 28,300 malformed login requests over roughly 20 seconds
- Blackpoint also successfully used the JavaBleed technique locally to read a secret stored next to the overflow in all 30 test runs
Neither independent group reproduced remote code execution, though crashes and memory leaks were confirmed. Oracle’s CVE record states that successful attacks “can result in takeover of Oracle Java SE.”
A proxy that waits for complete requests, as nginx does by default, blocks some attacks but not all. Failed attempts can crash Java, though attackers can often retry.
Who Is Exposed to This Java4Shell Vulnerability?
The vulnerable code affects specific Java versions on specific hardware:
- Java 17.0.6 and later on the Java 17 line
- Java 21, 25, and 27
- Java SE 8 Performance Pack build 8u511b33-perf
- GraalVM for JDK 17.0.21.0.3, JDK 21.0.13.0.3, and Enterprise Edition 21.3.20.0.3
Standard Java 8 and Java 11 are not affected. The vulnerability runs only on x86-64 chips with AVX-512 VBMI support, including Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids, and Granite Rapids chips, plus AMD Zen 4 or newer. ARM64 chips are not affected.
Organisations can check if their Linux servers have the required CPU features using:
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
All four features must appear in the output for the server to be vulnerable.
What This Means for Australian Organisations
Note: The following is general guidance and does not reflect claims from the source material.
Australian organisations running affected Java versions on enterprise applications should prioritise assessment and patching. General considerations include:
- The ACSC Essential Eight emphasises patching applications as a key mitigation strategy—this vulnerability underscores its importance
- Organisations subject to the Notifiable Data Breaches scheme should consider whether exploitation could lead to reportable incidents
- Critical infrastructure entities under the SOCI Act should assess whether affected applications form part of critical systems
OziTechs offers vulnerability management services to help Australian businesses identify and remediate critical flaws in their environments.
Actionable Recommendations
To address the Java4Shell vulnerability, organisations should take these steps:
- Identify affected systems—audit Java versions across your environment and check CPU capabilities
- Apply vendor patches immediately—Oracle’s fixed builds include 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1
- Monitor vendor advisories—Amazon has fixed Corretto builds, but Red Hat is still preparing fixes
- Review network architecture—reverse proxies may provide partial protection
- Implement monitoring—watch for unusual crash patterns or malformed requests
For comprehensive security monitoring and incident response capabilities, consider our managed security services.
Frequently Asked Questions
What is the Java4Shell vulnerability?
Java4Shell (CVE-2026-114938) is a vulnerability in Java’s Base64 decoder that can allow attackers to potentially execute code remotely on affected systems. It affects Java 17.0.6 and later versions running on x86-64 processors with AVX-512 VBMI support, impacting enterprise applications like Jira, Jenkins, and Keycloak.
How can I protect my organisation from CVE-2026-114938?
Apply the latest Java patches released by Oracle and OpenJDK this week. Check whether your servers use affected CPU types and Java versions. Review your exposure to affected applications and implement monitoring for suspicious activity patterns.
Is Java4Shell being actively exploited?
According to the report, Canada’s Cyber Centre stated it was not aware of any attacks exploiting the flaw. The researchers are holding back their attack code, and the vulnerability was not in CISA’s KEV catalog at the time of reporting.
Key Takeaways
- Java4Shell (CVE-2026-114938) can enable pre-authentication remote code execution on major enterprise applications
- The flaw affects Java 17.0.6+, Java 21, 25, and 27 on specific Intel and AMD processors
- Oracle and OpenJDK released patches this week—apply them immediately
- Independent researchers confirmed crashes and memory corruption but not remote code execution
- No active exploitation has been reported to date
Conclusion
The Java4Shell vulnerability represents a significant risk for organisations running affected Java versions on enterprise applications. While independent researchers have not yet reproduced full remote code execution, the confirmed memory corruption and crash capabilities—combined with the pre-authentication attack vector—warrant immediate attention.
Australian organisations should prioritise patching and assess their exposure to this Java4Shell vulnerability across their application landscape. If you need assistance identifying vulnerable systems or implementing patches, speak with our security team today.
