Java4Shell: Critical RCE in OpenJDK Base64 Decoder
Original: Java4Shell: RCE in OpenJDK when processing Base64
Why This Matters
OpenJDK underpins critical infrastructure globally; pre-auth RCE at this scale is rare.
Researchers disclosed CVE-2026-114938, a memory-corruption bug in OpenJDK's Base64 decoder scoring 9.2 CVSS 4.0. Pre-auth RCE confirmed in Keycloak, Jira, Confluence, Jenkins, and Artifactory in default configs.
Security firm Calif Research has disclosed Java4Shell (CVE-2026-114938), a memory-corruption vulnerability in OpenJDK's optimized Base64 decoder that enables unauthenticated remote code execution across a wide range of enterprise Java applications. The bug lives in hand-rolled AVX-512 VBMI assembly code used to accelerate Base64 decoding on x86-64 processors. A malformed input—just 64 'A' characters followed by a single '='—causes OpenJDK to miscalculate a negative output length, triggering a 64-byte write that overflows a 50-byte heap array by 62 bytes. On older OpenJDK 17, the trigger requires 128 'A' characters. The researchers confirmed pre-auth RCE in Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate running default configurations. Post-auth RCE was demonstrated in Apache Kafka, Solr, Elasticsearch, Gerrit, and Spinnaker. RCE was also confirmed in apps built on Apache Struts and Spring Boot. Researcher samczsun contributed a client-side exploit: a Java program opening a TLS connection to a malicious server can be compromised even if it exposes no public-facing service. The heap overflow can also be used to read adjacent memory in the style of the 2014 Heartbleed bug. Java powers an estimated 90% of Fortune 500 companies and ranks as the world's third most popular programming language.