java4shell-cover

Java4Shell: What We Know Now and What Comes Next

November 17, 2026

Java4Shell: What We Know Now and What Comes Next

Book a Demo

Update: OpenJDK, Oracle, and Calif have now published. This post reflects the official advisories, Calif’s full write-up, and our own lab results.

Java4Shell (CVE-2026-114938) is a heap out-of-bounds write in OpenJDK’s hardware-accelerated Base64 decoder. It leaked before its patch, and it is now confirmed by OpenJDK and fixed in Oracle’s 17 November builds. Calif’s write-up shows it can leak heap memory and lead to pre-authentication remote code execution.

TL;DR

Calif discovered and reported Java4Shell. On 17 November, the OpenJDK Vulnerability Group confirmed it, Oracle shipped fixed builds, and Calif published its technical write-up. We flagged it early on X, reproduced the bug on an AWS c6i instance, and are handling it as an urgent event.

  • It is confirmed and patched. OpenJDK scores it CVSS 3.1 8.1 (9.2 under CVSS 4.0), and Oracle’s fixed builds end in .1.
  • Java 17.0.6 and later, 21, 25 and 27 are affected. Standard Java 8 and 11 are not, but Oracle lists its Java 8 performance build as affected.
  • It needs specific hardware. Only x86-64 CPUs with AVX-512 VBMI run the vulnerable code. ARM is not affected.
  • Calif demonstrated pre-auth RCE in six major products. Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, all in default configurations.
  • Clients are at risk too, not only servers. Calif reports a client-side exploit against a Java program that connects to a malicious TLS server.
  • Patch, or turn off the Base64 intrinsic. -XX:-UseBASE64Intrinsics stopped the overflow on every affected version we tested.

Status: Fixed in Oracle’s builds. Fixes from other OpenJDK vendors are rolling out, so check your vendor. Calif is holding back its product-specific exploits for now. No exploitation in the wild reported yet, and not in CISA KEV.

What is Java4Shell?

A bug in the hand-written assembly that decodes the last few characters of a Base64 string. When a malformed string ends with a stray =, the decoder calculates a negative output length. That turns a small write into a full 64-byte write, 62 bytes past the end of the output array. Java rejects the input afterwards, but neighboring objects may already be corrupted.

Calif’s Quang Luong found it with AI assistance in about an hour, and built the first working exploit in two more.

Which versions are affected and fixed?

  • Java 17: 17.0.6 to 17.0.21 affected. Oracle fix: 17.0.21.1.
  • Java 21: up to 21.0.13 affected. Oracle fix: 21.0.13.1.
  • Java 25: up to 25.0.5 affected. Oracle fix: 25.0.5.1.
  • Java 27: up to 27.0.1 affected. Oracle fix: 27.0.1.1.
  • Java 8: Oracle lists 8u511b33-perf, its Performance Pack build, as affected. Standard Java 8 has no vulnerable decoder.
  • Not affected: Java 11 and Java 17.0.0 to 17.0.5.
  • Other OpenJDK builds: Corretto, Temurin, Microsoft, Zulu, Liberica, SapMachine, Red Hat OpenJDK and Oracle GraalVM all carry the same code. Take fixed versions from each vendor. In our lab, Temurin 17.0.21, 21.0.13 and 25.0.5 were vulnerable.

Who is exposed?

All of these must be true:

  • An affected JVM. Including Java runtimes bundled inside products.
  • An x86-64 CPU with AVX-512 VBMI. Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4 or newer. In AWS terms, that includes families such as c6i, m6i, c7i, c7a and m7a. On Linux, the CPU flags must include avx512f, avx512bw, avx512vbmi and bmi2.
  • Untrusted Base64 reaching Base64.getDecoder() or getUrlDecoder(). Authentication headers, tokens, file uploads and network messages are typical paths.
  • A JIT-compiled decoder. True on any busy service.

The same image can be exposed on one node and safe on another, depending on the CPU underneath it.

Is this remote code execution?

Yes. Calif demonstrated it, with real limits.

  • Pre-auth RCE: Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, in default configurations.
  • Post-auth RCE: Kafka Broker, Solr, Elasticsearch, Gerrit and Spinnaker. Calif also showed RCE in sample Struts and Spring Boot applications, and says the lists are not exhaustive.
  • Heap leak first: before code execution, the same technique can read Java heap memory, which may hold tokens, keys and personal data.
  • No universal exploit: each product needs its own heap layout and timing. Some chains depend on network conditions and on partial request bodies, so request-buffering proxies break some of them, but not all.
  • Failed attempts can crash the JVM, and attackers can retry.

Calif is holding back its product exploits for now and has published only a safe reproducer. Expect others to build working chains quickly.

What did we confirm in our lab?

We reproduced the overflow on an AWS c6i instance (Intel Ice Lake).

  • Affected: Temurin 17.0.6, 17.0.21, 21.0.13 and 25.0.5. Clean: Java 11.0.33 and 17.0.5.
  • Heap damage: with an exact-size output buffer, the overflow corrupted the next object in 97% of rounds and eventually crashed the JVM.
  • Pre-auth paths: Spring Security, Tomcat and Jetty 12 Basic auth, and Auth0’s java-jwt, pass attacker tokens straight to the vulnerable decoder.
  • Both stopgaps held on every affected version.

What is wrong in the advice going around?

  • “It’s Java 17 only.” Wrong. Java 21, 25 and 27 are affected too.
  • “It’s just a crash.” Wrong. Calif demonstrated heap disclosure and remote code execution.
  • “Add -XX:DisableIntrinsic=_base64_decodeBlock.” Wrong as written. On its own, this flag stops the JVM from starting. Pushed through JAVA_TOOL_OPTIONS, it is a fleet-wide outage.
  • “Set -XX:UseAVX=2 everywhere.” Risky. An ARM JVM does not recognize it and fails to start. Use it only on x86-64.
  • “Fixed in 17.0.11 and 21.0.3.” Wrong. That is JDK-8321599, an older bug in the same decoder. We reproduced Java4Shell on 21.0.13.
  • “Request buffering protects you.” Not reliably. Calif’s Elasticsearch chain works from a single complete request.

How can you detect attempts?

  • Request shape: a Base64-alphabet token of 32 characters or more that ends in = and whose length is not a multiple of 4. Start with Authorization headers.
  • Application logs: bursts of IllegalArgumentException from java.util.Base64$Decoder.
  • JVM crashes: unexplained hs_err_pid*.log files or bursts of restarts.

None of these proves compromise, and their absence does not prove safety. Patch first.

What should security teams do now?

  • Patch. Move Oracle JDK to its .1 builds and other runtimes to their vendor’s fixed release. Restart services and rebuild images.
  • Mitigate what you can’t patch tonight. Set -XX:-UseBASE64Intrinsics, which works on any architecture. Recreate containers so the setting reaches the running process.
  • Start with identity and CI/CD. Keycloak, PingFederate, Jenkins, Artifactory, Jira and Confluence on affected CPUs come first.
  • Inventory every JVM, not just packages. Bundled runtimes are easy to miss.
  • Don’t forget clients. Java programs that open outbound TLS connections need the same patch.

How is Upwind keeping you protected?

Our MDR team reproduced Java4Shell on real hardware and is handling it as an urgent event. Upwind tracks CVE-2026-114938 as critical, and the vulnerability feed for this CVE lists affected resources and which of them are exposed to the internet. Our analysts are joining that list with the CPU features of the nodes each workload runs on, to find the services that are truly at risk. We are shipping detection rules, hunting for the indicators above across customer environments, and contacting affected customers directly.

Upwind’s sensor sees the Java runtime each workload actually runs, including runtimes bundled inside products. At runtime it watches process lineage and crashes, so a Java service that keeps dying or spawns a shell is visible, whatever the exploit looks like.

To learn more about how Upwind finds exposed Java workloads and detects exploitation at runtime, schedule a demo.

Contents
Add the Upwind RSS Feed to Slack
Connect the Upwind RSS Feed to your Slack.
Follow the how-to here.
Threat RSS
Add the Upwind RSS Feed to Slack
Connect the Upwind RSS Feed to your Slack.
Follow the how-to here.
Main RSS