Skip to main content

Java4Shell: Patch OpenJDK Now, but First Check Whether Your Servers Have the Processor Feature It Needs

Calif.io says CVE-2026-114938, a Base64 bug in OpenJDK, lets attackers run code on Jira, Jenkins and Keycloak. It bites only on x86-64 servers with AVX-512 VBMI. Fixed Oracle builds, the CPU check, and two stop-gap flags.

Detailed close-up photo of a circuit board highlighting microchip components and electronic circuits.
KBY News Desk8 min read

In this article

Share

Oracle and the OpenJDK project released fixes on Tuesday 17 November for CVE-2026-114938, a memory-corruption flaw in the way OpenJDK decodes Base64 text, and the security firm that found it, Calif.io, has named it Java4Shell. Calif says an attacker who can get crafted Base64 into a vulnerable Java application can read the application’s memory or run code on the server, with no login needed on some of the products it tested, including Jira, Confluence, Jenkins and Keycloak. It also says the bug bites only on x86-64 servers whose processors support a feature called AVX-512 VBMI. As of Tuesday, Tenable said it knew of no reports of exploitation, and the flaw is not in CISA’s Known Exploited Vulnerabilities catalogue.

#Check the chip before you check the version

Most flaws are a question of software versions. This one has a hardware condition too, and that is the most useful thing for a busy admin to know. According to Calif, OpenJDK uses a hand-written routine built on AVX-512 VBMI instructions to decode Base64 quickly, and the bug sits in the code that handles the last few characters. On a processor without those instructions Java takes a different path and the flaw is never reached. Calif says that ARM64 processors are not affected.

Calif lists the families that qualify: Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD EPYC and Ryzen parts from Zen 4 onwards. On Linux you can see what a host reports by searching the CPU flags for avx512f, avx512bw, avx512vbmi and bmi2; Calif says all four must be present. In a virtual machine the flags are what the hypervisor passes through, so check from inside the guest, not from the purchase order.

Then the software. Calif says OpenJDK 17.0.6 and newer is affected. The OpenJDK Vulnerability Group’s advisory for 17 November lists the 17, 21, 25 and 27 lines, and Tenable’s reading of it is that standard Java 8 and Java 11 are not listed for this CVE. Oracle, which lists only the builds it supports and says earlier ones are likely affected too, names Java SE 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, plus the Java 8 Enterprise Performance Pack build 8u511b33-perf, and Oracle GraalVM builds for 17 and 21. Calif adds that the OpenJDK-based distributions are caught as well: Amazon Corretto, Eclipse Temurin, the Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine and Red Hat’s build.

#What the fixed builds are called

Tenable’s table of Oracle’s fixes, published on Tuesday, pairs each affected Oracle build with its replacement:

  • Java 17: 17.0.21.0.3 is fixed in 17.0.21.1
  • Java 21: 21.0.13.0.3 is fixed in 21.0.13.1
  • Java 25: 25.0.5.0.3 is fixed in 25.0.5.1
  • Java 27: 27.0.1.0.3 is fixed in 27.0.1.1
  • Java 8 Enterprise Performance Pack: 8u511b33-perf is fixed in 8u513-perf

For other distributions the same table gives no help, and Tenable says each vendor ships fixed builds on its own schedule. If you run Temurin, Corretto or a vendor build inside a container image, the question to ask is whether your base image has been rebuilt since Tuesday evening. An application that bundles its own Java needs the application vendor’s update, not a patch to the system Java.

#Which applications Calif says it broke

Calif says it demonstrated code execution before login, in default configurations, on Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate. After login it names Apache Kafka broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. It calls the list non-exhaustive, says ordinary features such as authentication and file uploads can reach the vulnerable decoder, and says a Java program that opens a TLS connection to a malicious server can be compromised even if it offers no service of its own. Calif also says there is no universal exploit: each application needs its own, and a failed attempt can crash the process.

We have not seen any of those vendors confirm Calif’s findings, and the claims come from Calif’s own testing. Calif says it is keeping its product-specific attack chains private until people have had time to upgrade. It has published a write-up and a proof of concept; Tenable says the proof of concept shows whether a given Java version and processor reproduce the bug but does not show whether a particular application is exposed. Separately, Kevin Breen of Immersive said on X that he had built a working, application-specific exploit and that Tomcat’s Basic authentication and the java-jwt library offer routes in before a user logs in. Tenable notes that his post does not say the exploit has been released.

#Where the severity numbers disagree

Oracle scores the flaw 8.1 under CVSS 3.1 and rates the attack complexity as high. Calif scores it 9.2 under CVSS 4.0. Both are fair readings of the same facts: Oracle is pricing in the hardware condition and the need for an application to pass untrusted data to the decoder, while Calif is pricing in how many ordinary applications do exactly that. Oracle’s own note, as Tenable relays it, says the flaw can be exploited only when an application passes untrusted data to the affected Java APIs.

The Register reports that CISA urged Java users to patch immediately, even though Oracle did not single the flaw out among the 655 patches in its November update, 62 of them rated critical. It also reports that Cisco’s Talos had seen no exploitation in the wild but expected probing to pick up after disclosure, and that Calif claims word of the bug leaked before the patches were ready. Jan Schaumann of Akamai, writing on the oss-security list, objected to what he called Calif’s focus on publicity. Whatever you think of the packaging, the facts in the vendor advisories stand on their own.

#Our view: urgent for some estates, a non-event for others

The name invites a comparison with the Java bugs that kept admins up for weeks, and we think that is half right. It is right in one respect: Java is everywhere in the middle of an enterprise, in identity, ticketing, build and search systems, and the products on Calif’s list are exactly the ones that sit in front of staff logins. It is wrong in another: a flaw that needs a particular processor feature and a per-application exploit will not hit everything at once. Expect it to be exploited against internet-facing Jira, Confluence, Keycloak and Jenkins servers first, because those are the targets Calif has shown can fall to it.

Our reading of the mechanism, as opposed to the vendors’ words, is that the AVX-512 condition will split estates in two. A mixed fleet of older on-premises servers may find only a handful of hosts qualify. A fleet that moved to current-generation cloud instances in the last two or three years may find most of them do. Do not assume; check. Hosts that really run on Arm are the easy exemption, since Calif says ARM64 is not affected.

We expect scanning for exposed products to start within days, since Talos already anticipates it. What would prove us wrong is a quiet week with no reports of attempts against the named products, and we would not take that as a reason to stop patching. If you cannot patch tonight, the decision is between a mitigation and an outage window, and we lean towards the mitigation now and the patch at the next window, for anything reachable from the internet.

#What to do today

Start with what faces the internet or sits in front of logins: Keycloak, PingFederate, Jira, Confluence, Artifactory, Jenkins. Work out which Java each one runs and whether the host reports the four CPU flags. Where both answers are yes, install the fixed build for your distribution as soon as it exists, or the application vendor’s update if Java is bundled.

Where you cannot patch yet, Calif names two startup options that keep the vulnerable code from running. One is -XX:-UseBASE64Intrinsics, which turns off the fast Base64 path. The other is -XX:UseAVX=2, which turns off AVX-512 and which Calif says must be used only on x86-64 hosts, because Java on ARM fails to start with it. Tenable points out that neither Oracle nor the OpenJDK group mentions these options, so treat them as Calif’s advice, test them first, and remove them once you are patched. Both need a restart of the Java process.

Finally, ask the vendors of anything you cannot patch yourself a direct question: “Which Java build ships in your product, and when is the fixed version available?” Write down the answer and the date. If you see crashes in a Java service after unusual requests, treat it as a possible probing attempt and keep the logs; Calif says failed attempts can crash the process.

#What we do not know yet

We do not know whether anyone is exploiting the flaw. Tenable and Talos said on Tuesday that they were not aware of attacks, and CISA’s catalogue did not list the CVE when we checked on Wednesday morning. We do not know the fixed build numbers for most distributions, because they had not all published at the time of writing. And we do not know how many applications beyond Calif’s list reach the vulnerable code. We will update this story if any of that changes.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01Calif.io: Java4Shell, write-up and recommendationscalif.io
  2. 02OpenJDK Vulnerability Advisory, 17 November 2026openjdk.org
  3. 03Oracle Critical Security Patch Update Advisory, November 2026oracle.com
  4. 04Tenable: Java4Shell frequently asked questionstenable.com
  5. 05Tenable: Oracle November 2026 Critical Security Patch Updatetenable.com
  6. 06The Register: Oracle reveals fix-this-ASAP-grade Java4Shell bugtheregister.com
  7. 07oss-security mailing list: CVE-2026-114938openwall.com
  8. 08CISA Known Exploited Vulnerabilities cataloguecisa.gov

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on Java4Shell: Patch OpenJDK Now, but First Check Whether Your Servers Have the Processor Feature It Needs. Comments are checked for spam and held for moderation before appearing.

Loading comments...

More news

All news

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.