Threat feed

Java4Shell OpenJDK RCE

Java4Shell corrupts OpenJDK's accelerated Base64 decoder into unauthenticated remote code execution

Posted · Spectrum Delta Research Team

Summary

Calif researchers (B/2) demonstrated that a memory-corruption flaw in OpenJDK's Base64 decoder, tracked as CVE-2026-114938 and nicknamed Java4Shell, lets a remote attacker with no credentials overwrite heap memory and execute code on x86-64 servers, with pre-authentication takeovers shown on default installations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. Oracle and OpenJDK shipped fixes on 17 November 2026 and Calif published its technical write-up the same day, including a public trigger of 64 A characters followed by an equals sign that writes 62 bytes past a 50-byte buffer, while withholding weaponized product exploits. Exploitation requires an x86-64 processor with AVX-512 VBMI, OpenJDK 17.0.6 or newer, and an application path that decodes untrusted Base64, which login headers, tokens and file uploads commonly reach before authentication; a heap-disclosure primitive Calif calls JavaBleed can leak keys and tokens. No exploitation in the wild is established at publication, and unpatched hosts can be mitigated with the JVM flags -XX:-UseBASE64Intrinsics or -XX:UseAVX=2.

Breakdown

Technical exposure

  • Java services on x86-64 CPUs with AVX-512 VBMI support
  • OpenJDK 17.0.6 or newer and distributions built from it
  • Application paths that decode untrusted Base64 before authentication
  • Internet-facing Keycloak, Jira, Confluence, Artifactory, Jenkins
  • Patched only in OpenJDK 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1

Adversary

Unknown (no exploitation in the wild established at publication)

Procedures (4)

  1. Malformed Base64 tail overruns the decoder's output buffer

    • T1190Exploit Public-Facing Application

    Logs

    • Web proxy or WAF logs · Inbound request to a Java application carrying a 65-character Base64 tail of 64 A characters followed by an equals sign (128 A plus equals on OpenJDK 17) in Authorization headers, tokens, cookies or upload parameters; the public trigger reaches login and token endpoints before authentication
  2. JVM crashes after heap corruption from the decoder overrun

    • T1499Endpoint Denial of Service

    Logs

    • JVM error logs and hs_err files · hs_err_pid files or SIGSEGV inside libjvm on the AVX-512 Base64 decode intrinsic, or a JVM exit immediately after a request with malformed Base64 input
  3. JavaBleed heap disclosure leaks keys and tokens into responses

    Logs

    • Web server access logs · Responses from Java endpoints whose size or content is anomalous after a malformed Base64 request; the reader primitive copies neighboring heap arrays, which may include private keys and session tokens, into application responses
  4. Code execution spawns from the Java application process

    • T1059Command and Scripting Interpreter

    Logs

    • EDR process and network events · Child process, shell, or outbound connection spawned by the Java application process shortly after a malformed Base64 request; commands run from the JVM working directory with no deployment-pipeline origin

Indicators of compromise

CVEs (1)

  • CVE-2026-114938heap out-of-bounds write in OpenJDK HotSpot AVX-512 Base64 decode intrinsic; pre-auth RCE demonstrated on default installs of six enterprise products

Sources

Questions, detections or sightings of Java4Shell OpenJDK RCE? Bring them to the community.