New: Citizen Developer Security | Let everyone develop. Securely.

See how

Blog

Java4Shell (CVE-2026-114938): unauthenticated remote code execution in Java 17, 21, 25 and 27

4 MIN

Java4Shell (CVE-2026-114938): unauthenticated remote code execution in Java 17, 21, 25 and 27

Oracle’s November 17, 2026 security update fixes CVE-2026-114938, a flaw that Calif found, reported and calls Java4Shell (The Hacker News). Oracle rates it 8.1 on CVSS 3.1: an attacker can exploit it over the network without credentials, with high impact on confidentiality, integrity and availability. Oracle places it in the Java SE Compiler component and lists Java SE 17.0.21, 21.0.13, 25.0.5 and 27.0.1 as affected, along with Java 8 in the Enterprise Performance Pack and GraalVM. Its replacement builds are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1.

Their write-up places the bug in the AVX-512 Base64 decoder of the HotSpot JVM from Java 17.0.6 on. It reports remote code execution in several widely used Java server products in their default configurations, some without authentication. OpenJDK’s advisory of the same day fixes it in the source shared by Eclipse Temurin, Amazon Corretto, Azul Zulu and the other OpenJDK builds. It lists 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3 and earlier as affected. Standard Java 8 and 11 are not affected.

Who is exposed

A service is exposed when all of these hold:

  • It runs on Java 17.0.6 or later, or Java 21, 25 or 27, on a HotSpot JVM: before your vendor’s fix, for example Eclipse Temurin, Amazon Corretto, Azul Zulu, SapMachine, Liberica, Microsoft, Red Hat or a Linux distribution package.
  • It runs on an x86-64 CPU with AVX-512 VBMI, such as Intel Xeon Ice Lake or later and AMD Zen 4 or later. ARM servers are not affected.
  • It passes input an attacker controls to the basic or URL decoder of java.util.Base64. Oracle notes that the flaw can be exploited by supplying data to the affected APIs, for example through a web service. Authentication headers, tokens and file uploads are common places where this happens.
Shift to AI podcast hosted by Roland Cloutier. Listen nowShift to AI podcast hosted by Roland Cloutier. Listen nowShift to AI podcast hosted by Roland Cloutier. Listen now

How to check if you’re exposed

  1. Find the Java version the workload runs. For a container image, run docker run --rm --entrypoint java <image> -version. On a host, run java -version.
  2. On the host that runs the workload, check the CPU with grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'. The host is affected only if all four flags print.

How Cycode helps

Two items on the Threat Intelligence dashboard query the Context Intelligence Graph across connected repositories and scanned container images:

  • Dockerfiles: lists Dockerfiles that build on a Java 17, 21, 25 or 27 image from Eclipse Temurin, Amazon Corretto, Azul Zulu, SapMachine, Liberica, Microsoft or distroless. Floating tags count until the image is rebuilt. Pinned tags count from 17.0.6 up to the builds the advisories list as affected.
  • Image runtimes: lists container images with a Java 17, 21, 25 or 27 runtime in the affected range, whether it comes from a JDK base image or a Debian, Ubuntu, Alpine or RPM package. Oracle’s replacement builds and later updates are left out. The count is the number of image repositories.

A match means the runtime is in the affected range. Exposure also depends on the CPU and on where the service decodes Base64.

See Cycode in action. Book a demoSee Cycode in action. Book a demoSee Cycode in action. Book a demo

What to do

  1. Move Oracle JDK workloads to Oracle’s replacement builds and rebuild their images.
  2. For other Java distributions, install your vendor’s build that includes the November 17 fix and rebuild every image that bundles Java. Until then, start the JVM with -XX:-UseBASE64Intrinsics or -XX:UseAVX=2, for example through JAVA_TOOL_OPTIONS. The second flag is x86-64 only: OpenJDK on ARM does not recognize it and fails to start.
  3. Start with internet-facing Java services on hosts where step 2 of the check prints all four flags.

Sources

Your complete Post-Mythos toolkit. Learn moreYour complete Post-Mythos toolkit. Learn moreYour complete Post-Mythos toolkit. Learn more