CVE Index中文
L3 · ShartedJava · OpenJDK · RCEjava4shell

Java4Shell turns OpenJDK Base64 decoding into conditional remote code execution

Calif published a PoC for CVE-2026-114938, a heap overwrite in OpenJDK's accelerated Base64 decoder. Exploitation needs an affected runtime, AVX-512 VBMI hardware and a reachable decoding path. Oracle released patches on November 17.

Disclosed
Nov 17, 2026
Public disclosure date
Severity
CVSS 8.1
1 CVE tracked here
Splash zone
Affected x86-64 JVMs with AVX-512 VBMI and attacker-controlled Base64 input; authentication depends on the application
java
In the wild
Not seen
Public PoC and researcher RCE demonstrations; no confirmed in-the-wild attacks found.

What happened

Java4Shell is a flaw in the JVM’s optimized machine code for Base64 decoding. Invalid padding can corrupt neighboring heap objects before Java rejects the input. Calif demonstrated memory disclosure and remote code execution through application-specific exploitation chains. A mainstream runtime and a public reproduction support L3; the reviewed sources do not confirm attacks against real victims.

Exposure requires the affected intrinsic to run on x86-64 hardware supporting AVX-512 VBMI and attacker input to reach that path. Calif traces the OpenJDK issue to 17.0.6 and later affected builds. Oracle separately names Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3; GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; and GraalVM Enterprise Edition 21.3.20.0.3. The Java 8 PERF listing does not mean all ordinary OpenJDK 8 builds are affected. OpenJDK’s per-CVE matrix does not mark 8 or 11 for this flaw.

Calif demonstrated pre-authentication RCE in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and authenticated RCE in Kafka Broker, Solr, Elasticsearch, Gerrit and Spinnaker. These are researcher-tested application paths, not evidence that every installation can be compromised. Calif also describes a client-side TLS path, so an inbound service is not always required. There is no universal payload, and product-specific weaponized chains remain private.

Apply the runtime supplier’s patch even when an application has no separate advisory. The table covers verified Oracle Java SE releases, not every distribution or GraalVM product. Until the correct supplier build is installed, disable the affected intrinsic and restart the JVM. Treat the log-preservation and credential-response steps above as general incident-response guidance, not published indicators of a confirmed campaign.

What’s in the bowl

CVE-2026-114938CVSS 8.1

OpenJDK Base64 intrinsic heap overwrite

Malformed padding reaches an out-of-bounds write in the x86-64 decoder; application-specific chains can leak memory or execute code. Oracle rates it 8.1 under CVSS 3.1; Calif rates it 9.2 under CVSS 4.0.

Fixed versions

ProductSafe fromNote
Oracle JDK 1717.0.21.1+4
Oracle JDK 2121.0.13.1+4
Oracle JDK 2525.0.5.1+4
Oracle JDK 2727.0.1.1+4
Oracle Java 8 Enterprise Performance Pack1.8.0_513-perf-b4

Can’t patch tonight? Plug the hole

JVM startup options
-XX:-UseBASE64Intrinsics

Restart every affected JVM with this option while arranging a patched build. Calif also offers -XX:UseAVX=2 on x86-64 only; ARM JVMs can fail to start with that flag.

Crime-scene timeline

  1. Nov 17, 2026

    Calif discloses Java4Shell and publishes a bounded PoC

    Researcher demonstrations include pre-authentication and authenticated RCE paths. Product-specific weaponized chains are withheld.

  2. Nov 17, 2026

    OpenJDK and Oracle publish security updates

    Oracle's CVE-specific matrix names affected Java SE and GraalVM builds; its release notes identify the patched Java SE builds listed here.

Who said what

We list each claim and who made it. Primary sources (the vendor, the researcher, the registry) are marked. Where reports disagree, we grade by the worst credible case.