Radar· local AI & agent security
security high confidence

Java4Shell (CVE-2026-114938): unauthenticated RCE in OpenJDK's Base64 decoder

Nov 17, 2026 · java, openjdk, cve, avx-512

TL;DR An out-of-bounds write in OpenJDK's AVX-512 Base64 fast path (17.0.6 and later, x86-64). Patched on Nov 17; workaround: -XX:-UseBASE64Intrinsics.

In plain words: modern Intel/AMD CPUs have special instructions (AVX-512) that Java uses to decode Base64 faster. That fast path has a bug: a carefully shaped input makes Java write past the end of a buffer, which an attacker can turn into running their own code.

What happened

The HotSpot JVM decodes Base64 with a hand-tuned AVX-512 routine. A short Base64 tail with padding makes it write about 62 bytes past the end of the array. Researchers showed remote code execution without login in Jira, Confluence, Jenkins and Keycloak; others only reproduced crashes and memory leaks. A public proof of concept exists, specific to each application. The bug was found with AI assistance.

Who is affected

  • OpenJDK 17.0.6 and later (including 21, 25 and 27),
  • on x86-64 CPUs with AVX-512 VBMI (avx512f, avx512bw, avx512vbmi, bmi2),
  • and only when the application decodes Base64 that comes from outside (tokens, auth headers, payloads).

ARM machines and CPUs without AVX-512 are not affected.

Why it matters

CVSS 4.0 is 9.2 according to the finder (Calif) and 8.1 according to Oracle. Base64 decoding of untrusted input is everywhere in Java web apps, and CISA asked for immediate patching.

What to do

  1. Apply your JDK vendor’s Nov 17 update.
  2. Can’t update yet: start the JVM with -XX:-UseBASE64Intrinsics (or -XX:UseAVX=2). JDK_JAVA_OPTIONS works too.
  3. Rebuild container images that ship their own JDK. Updating the host is not enough.

Sources

← back