Customers do not need to take any action on their Logit.io stacks in response to CVE-2026-114938, also known as Java4Shell.
Logit.io has reviewed the issue. Our review found most Logit.io platform components are not affected. A small number of internal processing servers, which are not exposed to public traffic, run an affected Java 21, and we are applying the mitigation to them anyway. The mitigation is being rolled out to the affected components as part of our normal patch management.
Contents
What the issue is
According to Tenable's FAQ on Java4Shell, CVE-2026-114938 is a memory corruption vulnerability in the part of Java that decodes Base64 data. Calif, the firm that found the flaw, reported it to Oracle. Tenable says Java uses a performance shortcut to decode Base64 faster on certain processors, and that when this shortcut receives a specially crafted Base64 string, it writes data beyond the memory it set aside. That can corrupt other information the application is holding in memory.
Cloudflare Radar's Java4Shell page cites Datadog Security Labs, which describes the flaw as an out-of-bounds write in OpenJDK that is reached before an application can reject the input, so the application's own validation does not protect it. In its key takeaways, Tenable records that Calif's testing showed attackers could run code without logging in on some widely used Java applications, such as Atlassian Jira and Jenkins.
Severity and affected versions
GitHub's advisory for the flaw, GHSA-6g7j-4xh3-xq2q, rates it High, with Oracle's CVSS 3.1 score of 8.1. Oracle's description in the advisory calls it a difficult to exploit vulnerability that allows an unauthenticated attacker with network access via multiple protocols to compromise the affected Java products. Oracle names the affected component as Compiler, and says the flaw can only be exploited by supplying data to APIs in that component, such as through a web service.
Oracle's list of affected builds in the advisory is Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3; Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; and Oracle GraalVM Enterprise Edition 21.3.20.0.3. Tenable notes that the Java 8 build on Oracle's list is its Enterprise Performance Pack, and that the OpenJDK Vulnerability Group lists the Java 17, 21, 25 and 27 release lines as affected.
Oracle released fixed Java builds on 17 November 2026, as part of its November 2026 Critical Security Patch Update. Tenable lists Oracle's fixed builds for this flaw as 8u513-perf (Java 8 Enterprise Performance Pack), 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.
Tenable says the flaw is in OpenJDK code, so other Java distributions built from OpenJDK can be affected, and that each vendor releases fixed builds on its own schedule. Cloudflare Radar adds that distribution packages and JDKs bundled in applications or container images can be affected too, and that fixed releases from vendors such as Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft and Red Hat may use build numbers that differ from Oracle's.
What conditions it needs
This is not a generic exploit. An attack has to be written for a specific application, and it needs three things at once: a CPU with AVX-512 VBMI, a vulnerable JDK and untrusted data reaching Java's Base64 decoder.
That matches Tenable's account. Tenable's key takeaways, citing Calif, say that only systems running an affected Java version on x86-64 processors that support AVX-512 VBMI can be affected. Tenable also cites Oracle as saying the flaw can only be exploited when an application passes untrusted data to the affected Java APIs. Tenable reports that researcher Kevin Breen described the same limits: the exploit is not generic and has to be adapted to each application.
As of 17 November 2026, Tenable said it was not aware of any reports that attackers have exploited this flaw. Tenable also reports that Calif has published a proof of concept that triggers the bug without taking control of the system, and is withholding exploits for individual applications for now, and that a second researcher has reported building a working exploit. Tenable notes that the researcher's post does not say the exploit has been released. Cloudflare Radar reports that Aikido had seen no reports of exploitation as of 17 November.
Logit.io does not use Apache Tomcat basic authentication or the java-jwt library, which Tenable reports researcher Kevin Breen identified as ways the flaw can be reached before a user logs in. Tenable also reports that Calif found applications including Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate could be exploited before login.
What we have checked, and what we are doing
Our review found most Logit.io platform components are not affected. A small number of internal processing servers run an affected Java 21. They are not exposed to public traffic, but we are not relying on that alone: Tenable reports Calif's account that a Java program can also be compromised when it connects over TLS to a server an attacker controls. The mitigation is being applied to these servers as well.
The mitigation is being rolled out to the affected components as part of our normal patch management. It uses the Java startup option -XX:-UseBASE64Intrinsics, which Tenable's FAQ, citing Calif, identifies as a way to turn off the Base64 performance shortcut that contains the flaw. We credit Calif for identifying it.
We will move to patched JDK versions as they become available, as part of regular image updates.
If you run Java yourself
If you run Java applications of your own, Cloudflare Radar recommends these steps:
- Find every Java runtime you run, including JDKs bundled in applications, distribution packages and container base images.
- Update each one to Oracle's 17 November patched build for its Java line or, for Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft, Red Hat or distribution builds, to that vendor's fixed release when it is available. Start with services that face the internet.
- Restart each updated service, because upgrading a package does not replace a Java process that is already running.
- Check the version each running process reports, not only the installed package.
For example, the first command below shows the version of a Java installation, and the second shows the version of a running Java process, where <pid> is its process ID:
java -version
jcmd <pid> VM.version
Where a patched build is not yet available for your Java distribution, Tenable's FAQ reports that Calif identified the Java startup option -XX:-UseBASE64Intrinsics as a way to keep the vulnerable code from running, by turning off the Base64 performance shortcut. Tenable notes that neither Oracle nor the OpenJDK Vulnerability Group mentions this option in its advisory.
Questions
If you have questions, please contact support.
Sources
- Oracle Critical Security Patch Update Advisory, November 2026
- GitHub advisory GHSA-6g7j-4xh3-xq2q
- Cloudflare Radar: Java4Shell, remote code execution in OpenJDK
- Tenable: Java4Shell (CVE-2026-114938) frequently asked questions
- CISA alert, 17 November 2026: Critical Java Vulnerability Requires Immediate Patching
- Calif: Java4Shell, Write once, RCE everywhere
