Java4Shell CVE-2026-114938: OpenJDK Base64 Bug Opens Pre-Auth RCE in Keycloak, Jira, Jenkins

Introduction

CVE-2026-114938, nicknamed Java4Shell, is a memory-corruption bug in OpenJDK's java.util.Base64 decoder. It lives in the AVX-512 VBMI–accelerated path that HotSpot uses on recent Intel Xeon and AMD Zen 4+ servers. Calif, which also found PHP2Shell, says attackers can use it to crash the JVM, read memory Heartbleed-style, or get unauthenticated code execution. Keycloak, Jira, Confluence, Jenkins, Artifactory and PingFederate can all be reached before login in default configurations. Oracle fixed it on November 17, and GreyNoise saw exploitation attempts the next day. Move to 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1, or your vendor's equivalent, and use the JVM flag below where you cannot update yet.

What Happened

Calif disclosed the bug on November 17, 2026, the same day as Oracle's November Critical Security Patch Update and a CISA alert telling Java users to patch immediately. Calif says the bug cost about $200 in AI tokens to find, and that word of it leaked before the fixes were out.

The flaw sits in HotSpot's intrinsic for Base64 decoding, an optimized x86-64 routine that decodes many bytes at once with AVX-512 VBMI instructions. A malformed Base64 string can push that routine into corrupting heap memory. Scoring differs depending on who you ask: Oracle rates it CVSS 3.1 8.1 (high attack complexity), and Calif rates it CVSS 4.0 9.2.

Calif's initial testing against default configurations found:

Reachable before login Reachable after login
Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, PingFederate Apache Kafka broker, Apache Solr, Elasticsearch, Gerrit, Spinnaker

The list is not exhaustive. Anything that Base64-decodes attacker input is a candidate, including HTTP Basic auth headers, SAML artifacts, JWT segments and file uploads.

Exploit status as of November 18–19:

  • Calif published a trigger-only PoC that checks the Java version and CPU but does not take control. It says application-specific exploits will follow.
  • Immersive and VulnCheck both say they have working exploits that need tailoring per application. Neither has released them.
  • GreyNoise recorded exploitation attempts and scanning for vulnerable Java versions, but no confirmed successful compromise.
  • Cisco Talos had not seen in-the-wild exploitation. The CVE was not in CISA KEV.

Why It Matters

This is a bug in the platform, not in an app. The applications Calif lists are the identity provider, the ticketing system, the wiki, the artifact store and the CI server. Between them they hold SSO signing keys, credentials, build secrets and the binaries you ship. Keycloak and PingFederate are especially bad places for a pre-auth memory read, because a leaked signing key lets an attacker mint tokens for every downstream app.

Two details make exposure easy to misjudge. First, the CPU decides whether you are vulnerable: the same container image is exploitable on a Sapphire Rapids node and safe on Graviton. Version-only scanners (Tenable says its plugins check version, not CPU) will flag both. Second, many products ship their own bundled JRE, so patching the OS OpenJDK package leaves Jira, Confluence or Keycloak containers untouched.

Who Is Affected

  • OpenJDK 17.0.6 and later, plus the 21, 25 and 27 lines, before the fixed builds below. Oracle also lists Java 8 Enterprise Performance Pack 8u511b33-perf and GraalVM builds. Standard Java 8 and 11 are not listed by OpenJDK.
  • Only x86-64 CPUs with AVX-512 VBMI: Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4 or newer. ARM64 is not affected.
  • Only when an application passes untrusted data to the affected Base64 APIs, which covers most web-facing Java servers.

Fixed builds by vendor:

Vendor Fixed
Oracle Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1; 8u513-perf
Oracle GraalVM JDK 17.0.21.1 / 21.0.13.1; EE 21.3.20.1
Eclipse Temurin 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 (rolling out)
Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK Fixed builds released
Ubuntu openjdk-17/21/25/27 fixed Nov 18
Red Hat RHEL OpenJDK fixed Nov 19; some bundled products such as Red Hat build of Keycloak still listed affected
Debian openjdk-21/25 fixed in Debian 13; openjdk-17 on Debian 12 still vulnerable at time of writing

How to Protect Yourself

1. Check whether your hardware is in scope

# all four flags present = vulnerable code path is available
grep -o -w -E 'avx512f|avx512bw|avx512vbmi|bmi2' /proc/cpuinfo | sort -u

# Kubernetes: which node CPU models are you running on?
kubectl get nodes -o custom-columns=NAME:.metadata.name,ARCH:.status.nodeInfo.architecture,LABELS:.metadata.labels | grep -iE 'amd64|x86'

ARM64-only fleets can deprioritize, but still patch, because workloads move between node pools.

2. Find every JVM, including bundled ones

# running JVMs and their real binaries
for p in $(pgrep -f java); do echo "$p $(readlink /proc/$p/exe) $(/proc/$p/exe -version 2>&1 | head -1)"; done

# bundled JREs inside application installs
find / -xdev -type f -path '*/bin/java' 2>/dev/null | while read j; do echo "$j: $("$j" -version 2>&1 | head -1)"; done

# container images
docker ps --format '{{.Names}}' | while read n; do echo "$n: $(docker exec "$n" java -version 2>&1 | head -1)"; done

3. Update to a fixed build

# Debian / Ubuntu
sudo apt update && sudo apt install --only-upgrade 'openjdk-*'
# RHEL family
sudo dnf upgrade 'java-*-openjdk*'

Rebuild images on a fixed base (eclipse-temurin:21.0.13.1_*, Corretto or Zulu equivalents), and pick up vendor releases for products that bundle their own JRE: Atlassian, Keycloak, Jenkins controller images, Artifactory, Elasticsearch.

4. Interim mitigation: disable the Base64 intrinsic

Calif's recommended stopgap, which Keycloak also documents, turns off the hardware-accelerated Base64 code:

# add to the JVM options for each affected service
-XX:-UseBASE64Intrinsics

# e.g. via environment for most launchers
export JAVA_TOOL_OPTIONS="${JAVA_TOOL_OPTIONS} -XX:-UseBASE64Intrinsics"

# confirm it took effect
java -XX:-UseBASE64Intrinsics -XX:+PrintFlagsFinal -version 2>/dev/null | grep UseBASE64Intrinsics

The broader alternative is -XX:UseAVX=2, which disables AVX-512 entirely. It costs more performance, and Java will not start with it on ARM. Neither flag is official Oracle or OpenJDK guidance. Both slow Base64 decoding, and both require a restart.

5. Hunt for crashes and post-exploitation

Failed attempts against this kind of bug tend to crash the JVM, and HotSpot leaves fatal error logs behind:

find / -xdev -name 'hs_err_pid*.log' -newermt '2026-11-17' 2>/dev/null
journalctl --since '2026-11-17' | grep -Ei 'java.*(SIGSEGV|core dumped)|A fatal error has been detected by the Java Runtime'

# JVMs spawning shells or downloaders
ps -eo pid,ppid,user,cmd --forest | grep -A2 '[j]ava ' | grep -E '/bin/(ba)?sh|curl|wget|python|nc '

If a Keycloak, PingFederate or other identity-provider JVM crashed unexpectedly after November 17, rotate its realm signing keys and client secrets.

Source