DEV Community

Cover image for Java4Shell (CVE-2026-114938): How to Check Your CPU and Java Version, and Patch
GeekSpark
GeekSpark

Posted on Originally published at geekspark.in

Java4Shell (CVE-2026-114938): How to Check Your CPU and Java Version, and Patch

On November 17, 2026, Oracle and the OpenJDK project shipped fixed Java builds for Java4Shell, tracked as CVE-2026-114938. It's a memory-corruption bug in the fast Base64 decoder that the Java runtime uses on newer x86-64 processors. Oracle rates it 8.1 (CVSS 3.1); Calif, the firm that found it, rates it 9.2 (CVSS 4.0).

Base64 malformed in one particular way (on Java 21 and later, 64 letter A's followed by a single =) makes the decoder write past the end of its buffer. Crashing an affected app is easy. Calif also showed remote code execution without a login on default setups of Keycloak, Jira, Confluence, Jenkins, JFrog Artifactory and PingFederate, though that takes app-specific work.

You're only exposed if two things are true:

  1. Your CPU supports AVX-512 VBMI (roughly Intel Ice Lake Xeons and AMD Zen 4 and newer). Check with grep -o -w -m1 -E 'avx512_?vbmi' /proc/cpuinfo. No output means the bug can't run there. ARM servers and Apple-silicon Macs are safe.
  2. You run Java 17.0.6 or later, or any Java 21, 25 or 27 build before the fix. Java 8 and 11 aren't affected by this bug.

The fixed versions are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. Mind the extra .1: 17.0.21 without it is still vulnerable. Ubuntu, Debian, Temurin, Corretto and Microsoft have shipped fixed builds, and fixed eclipse-temurin Docker images were out by November 20. Check apps that bundle their own Java too, such as Jira or Elasticsearch, because updating the system Java won't touch them. Restart every Java process after updating.

Can't update today? Start Java with -XX:-UseBASE64Intrinsics. It switches off only the faulty fast path, and Java falls back to its normal decoder. Confirm it's live with jcmd <PID> VM.flags -all | grep UseBASE64Intrinsics.

CISA urged immediate patching on November 17. As of November 18, nobody had confirmed a successful attack, but probing had started and unverified exploit code was already on GitHub.

Sources


This is the short version. The full guide, with every step and source, is on GeekSpark.

Top comments (0)