Java4Shell (CVE-2026-114938): Find and fix Java security vulnerability
This text was generated using artificial intelligence (AI).As of November 17, 2026, 11:30 PM CET – Updates are available, a test exploit is public. No active exploitation has been reported so far. Those running Java applications on current x86 servers should still update quickly.
Java4Shell is a vulnerability in the Java Runtime Environment identified by CVE-2026-114938. It lies in the Base64 decoder of OpenJDK, specifically in an accelerated machine code variant for x86 processors with AVX-512. Malicious Base64 data can overwrite memory behind the output buffer without requiring authentication. Affected are Java 17, 21, 25, and 27. On November 17, 2026, Oracle released updates, and the OpenJDK project issued a security advisory.
The name Java4Shell was given by the security company Calif, which discovered the vulnerability with its researcher Quang Luong. Calif had previously PHP2Shell made public. Oracle names Albert Yang as another reporter. In the assessment, there are two interpretations: Oracle and the OpenJDK project rate the vulnerability at CVSS 8.1 (v3.1, high) Calif and initial reports mention CVSS 9.2 according to CVSS v4.0 (critical). The official CVE entry has not yet been published.
Requirement: x86-64 processor with AVX-512 VBMI; ARM servers are not affected
Test exploit: public (only triggers the memory error); code execution reported only by Calif, attack chains not published
Patch available since: November 17, 2026
What's Behind Java4Shell?
Base64 is a common method for transmitting binary data as text, such as in login credentials, tokens, and file uploads. To decompress such data faster, the JIT compiler replaces the Java code of the decoder with a hand-optimized machine code routine, known as an intrinsic, after a short runtime. On x86 processors with AVX-512, this routine processes 64 bytes at a time.
The error lies in the handling of the last bytes and the padding character. =. With certain input lengths, the routine calculates a negative output length and, therefore, writes 62 or 63 bytes beyond the end of the output buffer into the Java heap. According to Calif, this is triggered by 64 instances of the letter „A“ followed by a =, while for Java 17 it is 128 instances of „A“ and =. Java itself properly rejects the invalid input; however, the memory has already been overwritten.
The affected optimization was proposed for the Java main line in June 2021 and later incorporated for Java 17. According to Calif, Java 17 is affected starting from version 17.0.6, which was released in January 2023.
Which systems are affected by Java4Shell?
A Java application is only affected if all three conditions are met:
Processor: x86-64 with AVX-512 VBMI. This includes Intel Xeon from Ice Lake (Sapphire Rapids, Emerald Rapids, Granite Rapids) as well as AMD EPYC and Ryzen from Zen 4. ARM servers such as AWS Graviton, Ampere, and Apple Silicon, as well as older x86 processors like Xeon Skylake, Cascade Lake, and AMD EPYC before Zen 4, are not affected.
Java version: Java 17, 21, 25 or 27 before the updates of November 17, 2026, as well as Oracle's Java 8 Performance Pack. Java 11 and regular Java 8 do not have the affected routine.
Base64 Usage: The application unpacks data from an insecure source using the Basic or URL decoder from java.util.Base64. The MIME decoder and libraries with their own decoder such as Jackson, JJWT, Nimbus JOSE+JWT, and Apache Commons Codec do not use the faulty path according to Equixly.
Typical entry points are according to Equixly credentials in the HTTP header Authorization: Basic, which Spring Security unpacks with java.util.Base64 before checking the password, as well as JWT segments that some libraries decode before signature verification. Calif mentions login functions and file uploads.
Important for inventory: Many Java applications bring their own runtime environment, for example in installation packages, appliances, or container images. Calif lists Oracle Java SE as well as Amazon Corretto, Eclipse Temurin, the Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, and Red Hat OpenJDK as affected, because they all build on OpenJDK.
Java4Shell Exploit: What Attackers Can Achieve
Opinions vary on the consequences:
Calif reports having leveraged the memory error via heap manipulation to read memory contents and execute code. According to their statements, this was possible in the default configuration without logging in to Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins, and PingFederate, with login required for Apache Kafka, Apache Solr, and Elasticsearch. A researcher also demonstrated an attack on Java programs that connect to a malicious server via TLS. Calif is withholding attack chains for the individual products for now; each application requires its own attack profile.
Equixly holds that after analyzing the source code, a crash of the Java runtime without authentication is substantiated, because the overwritten bytes are fixed and not chosen by attackers. Repeated attempts could cripple services.
Oracle and OpenJDK rate the vulnerability as having a high impact on confidentiality, integrity, and availability, but assign a high attack complexity.
So far, only a test program from Calif has been made public that safely triggers the memory error within its own buffer. This allows checking whether a runtime environment is affected. No active exploitation has been reported so far.
Check Running Java Version:jcmd VM.version shows the version of the currently running process. java -version only shows the first Java installation in the search path, not the bundled runtime of an application. With readlink -f /proc//exe the path of the used Java installation can be determined.
Check containers: Switch the base image in the Dockerfile to a patched Java version and rebuild. An image pinned to an old version remains vulnerable.
Bundled runtimes: For products with their own Java runtime, such as Atlassian installations or appliances, wait for and check the manufacturer's instructions.
Prioritize: First, services accessible from the Internet that accept basic credentials, JWTs, SAML messages, or Base64 uploads. Internal services that unpack data from other systems should also be included in the assessment.
Close Java security vulnerability: What to do now
Update Oracle Java SE to 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1 update, Java 8 Performance Pack and GraalVM to the status of the Oracle update from November 17, 2026.
Update Amazon Corretto to 17.0.21.1.2, 21.0.13.1.2, or 25.0.5.1.2 Update.
For other OpenJDK distributions and Linux packages, check the manufacturer’s advisory. The distributions have their own version numbers; Oracle's numbers cannot be directly transferred.
After the update, restart all Java processes. Replacing a package does not change a runtime environment already in use.
Inquire with hosted platforms and service providers whether the runtime environment has already been updated.
Transitional measures when the update is not yet possible
Calif mentions two startup options for the Java runtime that disable the faulty path:
-XX:-UseBASE64Intrinsics only disables the accelerated Base64 routine.
-XX:UseAVX=2 disables all AVX-512 optimizations and may slow down encryption and other compute-intensive functions. Set the option only on x86-64 systems; according to Calif, Java does not start on ARM with this.
Both options are default options of HotSpot, but Oracle has not confirmed them as a workaround for this vulnerability. Test before rollout and check with the restart. java -XX:+PrintFlagsFinal -version | grep -E ‚UseAVX|UseBASE64Intrinsics‘ Check.
In addition, access to unnecessary Java services and admin interfaces from the outside can be blocked. All known triggers are invalid Base64: they end with =, but do not have a length divisible by four. A web application firewall or an API gateway can reject such values, for example in the Authorization-header. None of these measures replaces the update.
How do I recognize an attack?
So far, there are no reliable indicators of attacks. Unexplained crashes of the Java runtime are considered a sign for closer examination, such as new crash logs hs_err_pid*.log. The crash often occurs later when other program parts access the corrupted memory; the log does not necessarily mention Base64. If any signs of compromise are found, one should assume that credentials, tokens, and keys from the affected process may be compromised and should be replaced.
DACH and EU Context
Timely implementation of security updates is one of the risk management measures for entities in the scope of NIS-2 according to Art. 21 of the NIS-2 Directive. If a significant security incident occurs due to an exploitation of Java4Shell, the reporting obligations according to Art. 23 of the NIS-2 Directive apply, in Germany according to § 32 BSIG. In Austria and Switzerland, the respective national reporting obligations apply.
How LocateRisk Addresses Exposed Assets
LocateRisk makes externally accessible systems and the software recognizable from the outside visible. With Java4Shell, this helps to find publicly accessible Java applications like Jira, Confluence, Jenkins, or Keycloak, including those not listed in any internal list, and to prioritize the update order. The automated Security Rating. With Preemptive Intelligence, LocateRisk reports critical software versions as soon as a vulnerability is known, even before the NVD officially categorizes it.
LocateRisk does not replace patch management. Whether a vulnerable Java version is running on a detected system, what processor is underneath, and whether the application unpacks Base64 data with the affected decoder cannot be determined from the outside. For this, internal inventory and matching with vendor advisories are necessary.
For outsourced applications and hosted platforms, vendor risk management can also help to reliably document feedback from service providers regarding the patch status.
Am I affected?
Affected are Java 17, 21, 25, and 27 before the updates mentioned in the table above, as well as Oracle's Java 8 Performance Pack, each only on x86 processors with AVX-512 VBMI. Anyone who wants to know if Java applications in their externally accessible infrastructure are even visible can use the CVE Quick Check Use the tool at the end of this article: It shows exposed systems and the software that is visible from the outside.
It is not always possible to determine the specific version that has been installed from the outside—the key factor is comparing it with the manufacturer's advisory.
Java4Shell is the name under which the Java security vulnerability CVE-2026-114938 is discussed. It is a heap overflow in the accelerated Base64 decoder of OpenJDK on x86 processors with AVX-512. Prepared Base64 data can overwrite memory behind the output buffer.
Java 17 (according to Calif from 17.0.6), 21, 25, and 27 before the updates of November 17, 2026, as well as Oracle's Java 8 Performance Pack. Java 11 and regular Java 8 are not affected. Additionally, the processor must support AVX-512 VBMI; ARM servers are not affected.
Public is a test program from Calif that triggers the memory error but does not execute any code. Calif reports code execution in several widely used Java applications but withholds these attack chains. Equixly only considers a crash of the Java runtime to be substantiated so far. No active exploitation has been reported.
Oracle Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, released on November 17, 2026, as well as Amazon Corretto 17.0.21.1.2, 21.0.13.1.2 and 25.0.5.1.2. Other OpenJDK distributions use their own version numbers; the respective vendor advisory is authoritative.
Java with -XX:-UseBASE64Intrinsics Start by blocking access to unnecessary Java services from the outside and rejecting invalid Base64 values at the gateway. The startup option is not confirmed by Oracle as a workaround and should be tested beforehand.
First points of contact are the OpenJDK advisory, Oracle's Critical Security Patch Update, and the advisories of the respective Java distribution. Those who do not operate Java applications themselves, such as with hosting platforms or service providers, should contact the provider directly and inquire about the patch status.
As of November 17, 2026. This article is for general informational purposes and does not constitute legal, security, or specific action advice. The IT security situation and patch availability may have changed since publication; the linked vendor advisory is always authoritative. Despite careful research, we make no warranty for the timeliness, accuracy, and completeness.
CVE Quick Check
In just a few minutes, check whether there are any indications of a current CVE on your externally visible attack surface.
Initial assessment in just a few minutes via email.
Learn more during a free consultation with a LocateRisk consultant.
You'll receive this by email
companyYour Company, LLC
Verified CVECVE-2026-114938
Passive Assessment
Information About the CVEfound or not found
Want to find out more, book a demo or simply exchange ideas? We look forward to hearing from you!
We use cookies to optimize our website and our service.
Functional
Always active
Technical storage or access is strictly necessary for the lawful purpose of enabling the use of a particular service expressly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a message over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that have not been requested by the subscriber or user.
Statistics
The technical storage or access, which is carried out exclusively for statistical purposes.Technical storage or access used solely for anonymous statistical purposes. Without a subpoena, the voluntary consent of your Internet service provider, or additional records from third parties, information stored or accessed for this purpose alone generally cannot be used to identify you.
Marketing
Technical storage or access is necessary to create user profiles, to send advertisements, or to track the user on a website or across multiple websites for similar marketing purposes.