The Java4Shell vulnerability is a critical flaw in OpenJDK, the most popular Java runtime. Calif disclosed it as CVE-2026-114938 and rates it 9.2 out of 10 (CRITICAL) under CVSS 4.0. According to Calif, a remote attacker without credentials can overwrite heap memory, read it in the style of Heartbleed, and reach remote code execution. Calif also says Java is the world’s third most popular programming language and powers 90 percent of Fortune 500 companies.
What is the OpenJDK Base64 vulnerability? Base64 is a common way to represent binary data as text. It is used in authentication protocols, file uploads and network messages. To decode it faster, OpenJDK uses specialized x86-64 CPU instructions, and the bug sits in the hand-written assembly code that handles the final characters.
Calif says an input of 64 A characters followed by a single = triggers the bug. In older OpenJDK 17, the input needs 128 A characters. The routine calculates a negative output length, so 62 bytes are written past the end of a 50-byte result array. Java rejects the input in the end, but neighboring objects may already be corrupted.
Calif demonstrated pre-auth remote code execution in Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate, all in default configurations. Post-auth attacks worked against Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. Calif stresses that these lists are not exhaustive. A client-side exploit shared by samczsun shows that a Java program opening a TLS connection to a malicious server can be compromised too.
AI played a big role. According to Calif, researcher Quang Luong needed one hour to find the flaw and two more hours to build the first working exploit. The total token cost was less than $200. Calif notes there is no universal exploit, because each application uses Base64 in a different way.
Calif calls for what it names vibe-uncoding. This means using AI to flag dead code and needless features, then removing them to reduce the attack surface. The reasoning is simple, because code you never needed still runs on your systems and still carries risk. Start by checking which of your systems run on OpenJDK and which features you can switch off.
Read calif.io article for more information.