On November 17, 2026, Oracle and the OpenJDK project released fixes for a critical security flaw in Java. The flaw is known as Java4Shell and is tracked as CVE-2026-114938. The researchers who found it, at security firm Calif, showed that on many common business applications it lets an attacker run their own code on a server without logging in. That can mean taking control of the server. Calif rates it 9.2 out of 10 for severity.
The same day, CISA, the US cybersecurity agency, put out an alert urging organizations to patch it immediately.
The short version: find out where Java runs in your business, including inside other software and appliances, apply the November Java updates or vendor patches, and restart the affected programs. Start with anything that can be reached from the internet.
What Java4Shell is
Java is one of the most widely used software platforms in the world. Many business programs run on it, even when you never see the word Java. The flaw sits in a small piece of Java that decodes Base64, a common way of turning files and data into text. Base64 shows up in logins, file uploads and network messages, so ordinary features of an application can reach the flawed code.
You do not need the technical details to act on this. What matters is that a carefully built piece of input can corrupt Java's memory. According to the researchers, that can leak sensitive information from memory or let an attacker run code.
Who is at risk
Java4Shell affects Java 17 and newer, including versions built from OpenJDK such as Oracle Java SE, Microsoft Build of OpenJDK, Amazon Corretto, Eclipse Temurin, Azul Zulu and Red Hat OpenJDK. The OpenJDK advisory lists Java 8 and 11 as not affected by this particular flaw.
There is also a hardware condition. The flawed code is only used on x86-64 processors that support a feature called AVX-512 VBMI. Calif lists recent Intel Xeon server processors (Ice Lake and newer) and AMD EPYC and Ryzen processors from the Zen 4 generation onward. ARM processors are not affected.
Calif showed working attacks without a password against Atlassian Jira and Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederate, all in their default settings. It also showed attacks that need a login against Elasticsearch, Apache Solr, Apache Kafka and others. The researchers say the list is not complete and that there is no one-size-fits-all attack, so each application has to be looked at.
The easiest place to miss Java is inside other products. CISA notes that Java runtimes are often bundled with third-party applications, container images and appliances, and may not show up as a separate item on a software list.
How to fix it
Apply the Java updates released on November 17, 2026, from Oracle or from whoever supplies your Java, then restart every Java program so the fix takes effect. For software that bundles its own Java, watch for an update from that vendor and apply it when it arrives. CISA advises putting internet-facing systems first.
A stopgap, not a fix. If a system cannot be updated right away, Calif says the flaw can be blocked by starting Java with the setting -XX:-UseBASE64Intrinsics, which turns off the faster decoding that contains the bug. Your IT provider will know how to add this. CISA also suggests limiting who can reach the system from the internet until it is patched. Treat these as a way to buy a little time, not a reason to wait.
Why this week matters
The researchers have published details and a basic proof of concept, though not their full attack code. Calif says it found the flaw with the help of an AI coding assistant in about an hour and built a first working attack in a couple more. When finding and using a flaw is that fast for defenders, it can be fast for attackers too, so the window between the fix and real attacks may be short.
Questions to ask this week
If someone else runs your servers or software, these questions will get you a clear answer quickly:
- Which of our servers and applications run Java, including programs that bundle their own copy?
- Are any of them Java 17 or newer, on servers with recent Intel Xeon or AMD processors?
- Are any of them reachable from the internet, such as a portal, a ticketing system or a login page?
- Have the November 17 Java updates or vendor patches been applied, and were the programs restarted?
- For anything that cannot be patched yet, what temporary protection is in place?
Not sure where Java runs in your business, or whether your servers and appliances have the fix? We can check your systems, find the Java hiding inside your software and help you get it patched. Call 713.980.2000 or send us a note.
Let's Talk →