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.