News and insights

Java4Shell: a flaw in Java that reaches common business software

On 17 November 2026, researchers disclosed a flaw in Java that they call Java4Shell (CVE-2026-114938). The same day, Oracle released fixed versions of Java. The researchers ran their own code, without signing in, on common applications such as Jira and Jenkins.

No attacks have been reported so far. But Java runs inside a great deal of business software, often out of sight, and some fixes are still to come.

What happened

Calif, a security research firm, published the details. The flaw is in the part of Java that decodes Base64, a common way of sending data as text. Specially crafted data can make Java write past the end of the memory it set aside.

Calif says this can let an attacker read memory, crash the program or run code on the server. Calif scores it 9.2 out of 10, Oracle 8.1. Red Hat rates it critical.

The flaw only matters under two conditions:

  • The Java version. OpenJDK 17.0.6 and later, including Java 17, 21, 25 and 27. That covers Oracle’s Java and others built from the same code, such as Amazon Corretto, Eclipse Temurin and Azul Zulu. Standard Java 8 and 11 are not affected.
  • The processor. Only x86-64 processors with a feature called AVX-512 VBMI, such as Intel Xeon (Ice Lake and newer) and AMD Zen 4 or newer. ARM processors are not affected.

Calif ran code without a sign-in on default installations of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate. With a sign-in, it did the same in Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker. It says these lists are not complete. It is holding back its attacks on specific products for now.

Other researchers have reproduced crashes, but not yet code execution. No attacks had been reported by 17 November.

Oracle’s fixed versions are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Amazon Corretto and Azul Zulu have also released fixes. Red Hat said it was “expediting the release of fixes”. Other distributors were still to follow.

What to do now

Security agencies and researchers give the same advice. List every Java runtime, with its supplier and full version, and update as soon as possible. Start with systems reachable from the internet. Look too for products, appliances and containers that bring their own copy of Java.

Where an update must wait, Calif and Red Hat give a temporary setting, -XX:-UseBASE64Intrinsics, which switches off the faulty code. Remove it once the fixed version is installed.

The Blueprint requirements this tests:

  • RW-DEV-02 A list of the software and services you run (Foundation). “Keep a current list of the software installed on your devices and servers, and of the cloud services you use, showing the version of each where it has one and who looks after it.” Would your list show Java hidden inside other products?
  • RW-DEV-10 Critical weaknesses fixed within 48 hours (Established). Internet-facing Java applications, such as Jira or Jenkins, fall into this group.
  • RW-DEV-20 Third-party code kept free of known flaws (Established). If you build software in Java, update the runtime it ships with and rebuild any container images.
  • RW-NET-18 Everything exposed to the internet is known (Established). Knowing which Java services the internet can reach tells you what to fix first.
  • RW-DET-06 Urgent security warnings acted on (Foundation). Watch for fixes from each supplier whose product carries its own Java.

How RiskWitness helps

Is this already on our register? Risks. Most registers will already hold a risk such as “Attackers exploit a known flaw before our fixes are installed”. Java4Shell is a reason to review it now. Check its owner, scores and review date. If you don’t have one yet, add it.

Which suppliers does it involve? Suppliers. Link that risk to the suppliers whose software or appliances bring their own Java. Their record then shows the risk alongside their criticality and assurance evidence.

Who is updating what, and by when? Actions. Give each update an owner and a due date, including a supplier’s fix when it arrives. Overdue actions show on the dashboard.

Did it work? Controls. Link your patching control to the risk and map it to RW-DEV-10. Record a test once the updates are in, with its result.

What about systems we can’t update yet? Risk acceptance. Where you’re waiting on a supplier, record the acceptance with a reason and an expiry. If it’s outside tolerance, a named approver signs it off.

Does leadership know? Reports. Share a PDF report or slide deck showing the risk and the actions.

Every step is kept in a history that shows who did what and when, with the old and new values. Nobody can edit or delete it. When leadership, an auditor, a customer or a regulator asks how you handled Java4Shell, the answer is already written down.

Sources