Oracle released its November 2026 update on 17 November, and Datadog Security Labs published research the same day on CVE-2026-114938, which they call Java4Shell. The flaw sits in the optimized Base64 decoder that the Java just-in-time compiler uses on some CPUs. If your business runs a Java service, a self-hosted tool written in Java, or a container image that bundles a Java runtime, this checklist is for you. It was checked on 18 November 2026. The short record is at /security/java4shell-openjdk-base64-decoder/.

What is actually affected

Two sources describe the scope in different ways, and both matter.

Oracle’s CNA entry lists exact affected builds: Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3; Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; and Oracle GraalVM Enterprise Edition 21.3.20.0.3. The fixed Oracle releases use a different version format. The release notes give full version strings 17.0.21.1+4, 21.0.13.1+4, 25.0.5.1+4 and 27.0.1.1+4. Do not expect the two formats to line up character for character.

Datadog describes a broader range of OpenJDK builds, for example Java 17 from 17.0.6 up to releases before 17.0.21.1. Their research adds three conditions that all have to hold: a vulnerable runtime decoder, an x86-64 CPU that takes the AVX-512 VBMI execution path, and attacker-controlled Base64 data reaching that decoder. Native ARM64 JVMs do not execute the vulnerable path. Datadog states there is no universal exploit against every Java application.

Two cautions on Java 8 and 11. Ordinary Java 8 and Java 11 builds are not listed for this CVE, but Oracle does list 8u511b33-perf, so a flat statement that Java 8 is fine is not safe. Separately, the same November update fixes other issues in those families, so they still need their own review.

Step 1: inventory the runtimes you actually run

List every service, scheduled job and container image that includes Java. For each, note the vendor (Oracle, Eclipse Temurin, Amazon Corretto, a Linux distribution package, or a runtime bundled inside an application), the full build string, and whether the service accepts data from the internet. Runtimes bundled inside applications and images are the ones most often missed.

Step 2: check the CPU and the decoding path

Record whether each host or node is x86-64 with AVX-512 VBMI, or ARM64. Then ask the application owner or vendor whether untrusted input is Base64 decoded anywhere, such as in authentication headers, API payloads or file uploads. Datadog observed differences between the Basic/URL decoder path and the MIME path only on the 17.0.6 build they tested, so do not generalize that detail to other versions or to your own authentication setup. Catching IllegalArgumentException in application code is not a fix, because it does not undo memory writes that happened before the exception was raised. What matters is whether untrusted input reaches the affected decoder at all. Input handling that rejects or normalizes data before that point can change the outcome, but do not rely on application-level validation alone as a universal defense; the runtime update is the fix.

Step 3: pick the fixed build from your vendor, not from Oracle’s table

For Oracle Java SE 17, 21, 25 and 27, the release notes linked below confirm the fixed full version strings. For Oracle 8-perf and GraalVM, Oracle lists affected builds, but a CVE-specific fixed build was not independently verified at the time of checking, so ask Oracle support. For every other distribution, use that vendor’s own advisory and fixed package. Ubuntu, Debian and Red Hat backport fixes, so a package version that looks older than upstream can still contain the fix. Where a provider manages the runtime for you, ask the provider which build is deployed.

Step 4: update with a tested backup and redeploy

Take a backup you have actually tested restoring from, confirm the new runtime is compatible with the application, then update. For containers, update the base image, rebuild the application image and redeploy. Restart every affected Java process. A runtime update on disk changes nothing for a process still running the old one.

Step 5: verify the running JVM

Check the process itself, including bundled runtimes, rather than the java on your shell path or the installed package list. Where jcmd is available:

jcmd <PID> VM.version

If you cannot update yet

Datadog tested two JVM startup options that prevented the out-of-bounds writes in their tests: -XX:-UseBASE64Intrinsics, which is the narrower option, and, on x86-64 only, -XX:UseAVX=2. Native ARM64 JVMs do not recognize the UseAVX option and can fail to start if it is added to shared settings, and limiting AVX can affect performance. Treat either option as a temporary measure for the service owner to compatibility-test and restart, then verify the effective flags:

jcmd <PID> VM.flags -all

Confirm the process reports UseBASE64Intrinsics = false or UseAVX = 2, depending on the option chosen. A workaround is not a patch, and nothing here should be pushed blindly across a fleet.

What is still unknown

No real-world exploitation was established in the sources reviewed, and the CISA Known Exploited Vulnerabilities catalog of 17 November 2026 did not list this CVE. Absence from that list is not proof of absence. Fixed-build mappings for Oracle 8-perf and GraalVM, other vendors’ build numbers, and your own decoding and exposure details remain to be confirmed per deployment.

Sources