On November 17, security firm Calif disclosed Java4Shell (CVE-2026-114938), a memory corruption vulnerability in OpenJDK’s Base64 decoder. Calif scores it 9.2 under CVSS 4.0, while Oracle rates it 8.1 (High) under CVSS 3.1. Patches went out the same day alongside an OpenJDK advisory and Oracle’s November 2026 Critical Security Patch Update. CISA issued an alert the same day, and CERT-EU followed on November 18.
What makes Java4Shell particularly dangerous is that the flaw is in the Java runtime itself, not in any single framework or library. Calif’s testing showed unauthenticated remote code execution against Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins, and PingFederate, all in their default configurations. Calif recommends all Java users should update immediately.
Java4Shell Background and Attack Mechanism
Calif researchers found and reported Java4Shell, and Calif says it used AI to find and weaponize it: about an hour to discover the vulnerability and two more to build the first working exploit, for under $200 in tokens.
The bug is in HotSpot’s hand-tuned x86-64 assembly for decoding Base64, which uses AVX-512 instructions. When input ends in certain padding patterns (such as = or ==), the routine miscalculates how many bytes to write and stores a full 64-byte block, writing past the end of the output buffer. In Calif’s example, 65 bytes of input produce a 50-byte buffer, and 62 bytes land past its end. That heap out-of-bounds write can be turned into code execution. The fast path only kicks in after the JIT compiler has optimized the decoder, which happens on servers that decode Base64 routinely.
A service is exposed when all three of these are true:
- It runs OpenJDK 17.0.6 or newer, which covers Oracle Java SE, Oracle GraalVM, and every major OpenJDK build (Eclipse Temurin, Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Red Hat, BellSoft Liberica, and SAP SapMachine).
- OpenJDK 8, OpenJDK 11, and Java 17.0.0 through 17.0.5 are not affected. The one Java 8 exception is Oracle’s Java SE 8 Enterprise Performance Pack, which is affected.
- It runs on an x86-64 CPU with AVX-512 VBMI, such as Intel Xeon Ice Lake or newer, or AMD Zen 4 or newer.
- ARM64 CPUs are not affected.
- The application decodes attacker-controlled Base64, which ordinary features like authentication and file uploads do.
To check a Linux host’s CPU, Calif suggests the command below. If the output includes all four flags, the CPU can reach the vulnerable code.
grep -m1 '^flags' /proc/cpuinfo \
| tr ' ' '\n' \
| grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'The impact goes beyond the products above. Calif also showed post-authentication RCE in Apache Kafka, Apache Solr, Elasticsearch, Gerrit, and Spinnaker, as well as sample apps built on Spring Boot and Apache Struts, and notes the lists are not exhaustive. Clients are at risk too: a Java program that opens a TLS connection to a malicious server can be compromised. There is no universal payload, so each exploit is built per application. Calif has published a small proof of concept that triggers the memory corruption, and is keeping its product exploit chains private until users have had a chance to upgrade. Third-party proof-of-concept code and detection rules have since appeared on GitHub. As of November 18, no exploitation in the wild has been confirmed.
Patching the Java Vulnerability
Update every Java runtime to a fixed build. The upstream fixed releases are:
| Java line | Vulnerable (latest Oracle build before the fix) | First fixed release |
|---|---|---|
| 17 | 17.0.21.0.3 and earlier (back to 17.0.6) | 17.0.21.1 |
| 21 | 21.0.13.0.3 and earlier | 21.0.13.1 |
| 25 | 25.0.5.0.3 and earlier | 25.0.5.1 |
| 27 | 27.0.1.0.3 and earlier | 27.0.1.1 |
| Oracle Java SE 8 Performance Pack | 8u511b33-perf | 8u513-perf |
Watch the version strings closely. A runtime that reports 17.0.21 or 17.0.21.0.3 looks current but is still vulnerable. Only 17.0.21.1 and later include the fix.
OpenJDK distributions ship on their own schedules and use their own version strings. Status as of November 18:
- Amazon Corretto: Fixed in 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, and 27.0.1.1.4, with matching Amazon Linux packages.
- Azul Zulu: Fixed in 17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2, and 27.0.1.1+4.
- Eclipse Temurin: Fixed in 17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2, and 27.0.1.1+4. Binaries are rolling out as testing completes, and updated
eclipse-temurinimages land on Docker Hub once all binaries for a JDK version are published. - Red Hat build of OpenJDK: Fix pending; see Red Hat security bulletin RHSB-2026-018.
- Debian and Ubuntu: A fixed openjdk-21 package reached Debian unstable on November 18. Debian stable and Ubuntu packages were not yet fixed.
- Microsoft, BellSoft Liberica, SAP SapMachine: Affected; check each vendor’s advisory for fixed builds.
Then rebuild container images on a patched base image and restart every Java process, because JVMs that are still running keep the vulnerable code in memory.
If you can’t patch right away, or your vendor hasn’t shipped a fix yet, Calif lists two JVM flags as workarounds:
-XX:-UseBASE64Intrinsicsdisables the hardware-accelerated Base64 code.-XX:UseAVX=2disables AVX-512. Use it only on x86-64 hosts: OpenJDK on ARM doesn’t recognize the flag and will fail to start.
Unsupported Java releases, including 18–20, 22–24, and 26, may also be vulnerable and will not receive security fixes. Organizations still using them should migrate to a supported, patched Java version, and apply the JVM flag -XX:-UseBASE64Intrinsics in the meantime.
Don’t count on a proxy to protect you. Calif notes that request buffering is not a general mitigation.
Safe versions: 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1, or later for your Java line (8u513-perf for Oracle’s Java SE 8 Performance Pack). Downstream vendors use their own version strings, so confirm the fixed build in your vendor’s advisory. Restart every JVM after upgrading. The JVM flags above are a stopgap, not a fix.
Finding and Fixing Java4Shell with FOSSA
Java4Shell lives in the Java runtime, not in your application’s dependencies. Your build files never declare which JDK your app runs on, so a Maven or Gradle dependency scan won’t flag it. FOSSA can still detect it at the layer where the JDK lives. Container scanning and SBOM import pick up JDK packages installed by the Linux package manager (for example, openjdk-17 or java-21-openjdk) and match them against the CVE. Here’s how to use FOSSA to find and fix it.
- Scope: Use your FOSSA project inventory to list every Java project (Maven, Gradle, and so on). Each one runs on a JVM somewhere, so this is your candidate list. For each deployment, check the JDK version with
java -version(orjcmd <pid> VM.versionfor a running process) and run Calif’s CPU check above. - Detect: Rescan your container images (or turn on scheduled scans). Container scanning flags vulnerable JDK and JRE packages installed by the OS package manager in base image layers, as Linux distributions publish their advisories. Some distributions haven’t shipped fixed packages yet, so an image may be flagged before an upgrade is available. Apply the JVM flags above to those images in the meantime. If your image unpacks a JDK from a tarball instead, as the official Eclipse Temurin images do, check its base image tag directly. You can filter the Issues inbox by CVE ID to see every affected image at once.
- Prioritize: Start with internet-facing services, especially those running the products Calif named: Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate. If you control your hardware (on-prem or bare metal), treat x86-64 hosts with AVX-512 VBMI as highest risk. If you run in the cloud and can’t confirm the CPU generation behind your instances, assume you may be affected and patch on the same timeline.
- Remediate: Move each image to a patched base image (or update the host’s JDK), then redeploy and restart. Upgrading application dependencies won’t fix this one.
If you have questions about using FOSSA to assist with Java vulnerability remediation, please reach out to your customer success contact, or get in touch with our team.
