On 17 November 2026, Oracle and the OpenJDK project fixed a security flaw in the Java runtime: CVE-2026-114938. Its finders at the security firm Calif call it Java4Shell, and many reports also call it Java2Shell. Calif rates it at CVSS v4.0 9.2, Oracle at 8.1 under the older CVSS 3.1 scale.

As with php2shell, the bug sits one level below the application. Jira, Confluence, Jenkins, Keycloak and many in-house applications inherit it from Java. One day later came two flaws in nginx, more on that here.

This article explains what Java4Shell is, under which conditions it applies and what to do now.

What is Java4Shell?#

At runtime, Java translates frequently used functions into particularly fast machine code. For decoding Base64 there is dedicated hand-written code for processors with the AVX-512 instruction set. Base64 is the format used, for example, for login data in the HTTP header or for parts of access tokens.

This is exactly where the bug sits. If Base64 input ends with a surplus padding character, the code miscalculates a write mask and writes up to 64 bytes past the end of the intended memory. Java then rejects the input with an error, but only after the memory has already been corrupted.

Calif describes two consequences: an attacker can read memory contents and, with enough effort, run their own code on the server. There is also a variant on the other side. A Java program that connects to a malicious TLS server can be attacked as well.

The flaw was found by Quang Luong of Calif using the AI agent Codex. According to Calif, it took one hour to find and two more hours to build the first working exploit. The compute cost was under 200 US dollars.

Who is affected? Three conditions#

Only systems that meet all three conditions are affected:

ConditionAffectedNot affected
Java versionJava 17 from 17.0.6, Java 21, 25 and 27, each before the fixJava 8 and 11 in the usual builds, Java 17 before 17.0.6, OpenJ9
Processorx86-64 with AVX-512 VBMI, for example Intel Xeon from Ice Lake and AMD EPYC from Zen 4ARM such as Apple Silicon and AWS Graviton, older x86 processors
Applicationdecodes Base64 from external requests, for example with HTTP Basic login or JWTapplications without such input

The second condition surprises many. Whether a system is vulnerable also depends on the hardware Java runs on. The same application can be affected on one server and not on another. In the cloud, a change of instance type can be enough to change that.

On Linux, this command shows whether the processor has the required features:

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

If all four values appear, the hardware condition is met. Check this inside the virtual machine itself, not on the host. Which processor features a VM sees depends on the CPU type configured in Proxmox, VMware or Hyper-V.

The third condition is particularly dangerous when the Base64 input is processed before login. Then an attacker needs no account.

Patched versions: 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1#

Oracle and OpenJDK published fixes on 17 November 2026. Oracle's builds:

  • Java 17: 17.0.21.1
  • Java 21: 21.0.13.1
  • Java 25: 25.0.5.1
  • Java 27: 27.0.1.1
  • Java 8 Enterprise Performance Pack: 8u513-perf

Branches 18 to 20, 22 to 24 and 26 get no fix. If you still run them, move to a maintained version.

Other vendors such as Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK or the Debian and Red Hat packages ship their own builds on their own schedule. Azul had the fix out within an hour, some Linux distributions take longer. What counts is the security notice of the respective vendor.

Which applications are affected#

According to Calif, it demonstrated a takeover without login in the default configuration of:

  • Keycloak
  • Atlassian Jira and Confluence
  • Jenkins
  • JFrog Artifactory
  • PingFederate

With login, it succeeded against Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker, as well as sample applications built on Spring Boot and Apache Struts. That means in-house applications are affected too. Calif stresses that the list is not complete.

For small and mid-sized businesses this means: the flaw hits tools that are often self-hosted and frequently reachable from the internet. The ticket system, the wiki, the build server, the central login. Keycloak deserves special attention, because whoever takes over the central login gets to every application behind it.

Many of these products ship their own Java runtime. What java -version shows on the server then says nothing about the version Jira actually runs on. The same applies to container images. The US agency CISA explicitly points out that such bundled runtimes are missing from many inventories.

How dangerous is Java4Shell?#

This is where opinions differ. Calif reports working attacks against the products listed and has published a video of them. Calif is holding back the product-specific exploits until updates have spread. What is public is the root cause, the technique and a harmless trigger that shows the bug.

Independent labs paint a more cautious picture so far. Harness reproduced the out-of-bounds write but did not achieve code execution, because the overwritten bytes cannot be chosen freely. OX Security estimates that fewer than 0.12 percent of all Java instances worldwide are open to a takeover, but around 0.8 percent can be crashed remotely. Every application needs its own attack chain, there is no universal exploit.

No attacks have been confirmed so far, and the flaw is not in CISA's catalogue of actively exploited vulnerabilities. The GreyNoise service has, however, seen first requests from a few addresses that match the Java4Shell pattern. CISA issued its own alert on 17 November and calls for immediate patching.

Our assessment: taking over a server is hard, crashing it is easy. For a ticket system or the central login, an outage alone is a serious problem. So there is no reason to wait.

Be careful with alleged exploits on GitHub: according to OX Security, fake repositories for this flaw often contain malware.

Stopgap: two switches for Java#

If you cannot update right away, switch off the faulty code when Java starts. There are two options:

  • -XX:-UseBASE64Intrinsics only switches off the fast Base64 decoder. Java then uses the slower but correct version. Applications that process a lot of Base64 become slightly slower.
  • -XX:UseAVX=2 drops AVX-512 entirely. This has a broader effect and costs more performance. Careful: on ARM processors, Java does not start with this switch.

Both switches only take effect after the application restarts. Where to set them depends on the product, for Jira and Confluence for example in setenv.sh, for containers via the JAVA_TOOL_OPTIONS environment variable. Afterwards, check on the running process that the switch is set.

A reverse proxy or a request size limit does not protect reliably. The malicious input is very short.

How we protect our clients#

Java runs in more systems than any inventory shows. As part of a managed service, this is how we handle Java4Shell:

We look for every Java runtime, not just the installed one. Including the ones Jira, Jenkins or Keycloak bring along, and the ones in container images. What counts is the version the process actually runs on.

We check the hardware too. With this flaw the processor matters, including the CPU type the hypervisor passes through to the virtual machine. We check this per system instead of raising a blanket alarm.

We prioritise by exposure. The central login and everything reachable from the internet without login comes first. Internal systems follow in the maintenance window.

We inform in both directions. Also when an environment is not affected, for example because it runs on ARM or uses Java 11.

We keep watching after the patch. Java crashes leave crash logs behind. If they show up on an exposed system, we look into the cause.

Patching Java4Shell in six steps#

If you run your systems yourself, this is the order:

  1. Find Java runtimes. List every system with Java, including runtimes bundled in products and container images. ps -ef | grep java shows the path of the runtime actually in use, <path>/java -version then shows its version.
  2. Check the hardware. Check the processor features with the command above, inside the VM. If avx512vbmi is missing, the system cannot be attacked this way. Patch anyway, because a move to newer hardware changes that.
  3. Apply the patch. The target is 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 or the matching build from your vendor. For products with their own runtime, apply the vendor update or replace the runtime following the vendor's instructions. Rebuild container images.
  4. Restart. A new Java build only takes effect once the application restarts. Afterwards, check the version on the running process.
  5. Ask vendors and providers. Ask software vendors and service providers for their status and get the answer in writing, especially for products that bundle Java.
  6. Look for traces. Search for unexpected crashes, recognisable by files named hs_err_pid*.log, and for bursts of Base64 decoder errors on input ending in =. If you find such traces on an exposed system, rotate passwords, keys and tokens the application held in memory.

Frequently asked questions#

Are Macs or servers with ARM processors affected?
No. The flaw only affects x86-64 processors with AVX-512 VBMI. Apple Silicon, AWS Graviton and other ARM systems do not use the faulty code.

Are Java 8 and Java 11 affected?
Not in the usual builds, which do not contain the faulty code. Exceptions are special builds such as Oracle's Java 8 Enterprise Performance Pack.

Is Java4Shell related to Log4Shell?
No. Log4Shell was a bug in the Log4j library in 2021. Java4Shell sits in the Java runtime itself. The name alludes to Log4Shell, the mechanism is a different one.

Does updating Jira, Confluence or Jenkins help?
Only if the update ships a fixed Java runtime or the application runs on a patched runtime of the system. What counts is the Java version of the running process, not the version of the application.

Is the flaw being exploited already?
As of 18 November 2026, no attacks have been confirmed. First matching requests have been observed, and both the root cause and the technique are public.

Conclusion#

Java4Shell is hard to exploit and easy to trigger. Whether an environment is affected comes down to three things: Java version, processor and application. If you can answer these three questions for your systems, the assessment is quickly done. The patch is available and the only complete answer.

More remarkable than the flaw is how it was found: an AI agent, one hour, under 200 dollars. After php2shell, this is the second case of its kind within four weeks, and nginx followed the next day. Old code in core building blocks is being searched at high speed right now, by defenders and attackers alike. Patch management has to keep up with that pace.

If you are weighing whether to carry this yourself, you will find the arguments in our comparison MSP or in-house IT admin.

Not sure where Java runs in your estate? Talk to us. We will check, and we will also tell you when no action is needed.

Sources#

  • Calif, disclosure, affected products and discovery with Codex
  • Oracle, Critical Security Patch Update November 2026
  • CISA, alert of 17 November 2026
  • JFrog Security Research, root cause, versions and preconditions
  • Harness, lab reproduction
  • OX Security, risk estimate
  • Qualys, detection and workarounds
  • Azul, fix in the 17 November builds