Skip to content

Calif discloses critical Java4Shell flaw in OpenJDK Base64 decoder

Oracle and OpenJDK released patches on November 17, 2026, while Cisco Talos reported no observed in-the-wild exploitation.

https://breach-signal.com/vulnerabilities/calif-discloses-java4shell-openjdk-base64-decoder-flaw/

Share

Key facts

  • Calif disclosed CVE-2026-114938, nicknamed Java4Shell, on November 17, 2026, as a critical memory-corruption flaw in OpenJDK's Base64 decoder enabling unauthenticated remote code execution.
  • Calif gave the vulnerability a CVSS 4.0 score of 9.2 and said any rating above 9 counts as critical.
  • The flaw reaches OpenJDK releases from 17.0.6 onward when executed on x86-64 chips supporting AVX-512 VBMI instructions.
  • Affected distributions include Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, Red Hat OpenJDK, and Oracle GraalVM for JDK.

Calif disclosed CVE-2026-114938, nicknamed Java4Shell, on November 17, 2026, as a critical memory-corruption flaw in OpenJDK’s Base64 decoder enabling unauthenticated remote code execution.

The flaw reaches OpenJDK releases from 17.0.6 onward when executed on x86-64 chips supporting AVX-512 VBMI instructions. Exposed distributions include Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, Red Hat OpenJDK, and Oracle GraalVM for JDK. ARM64 systems are not affected because the vulnerable optimization runs only on x86-64 chips with AVX-512.

Calif gave the vulnerability a CVSS 4.0 score of 9.2 and said any rating above 9 counts as critical. Oracle assigned CVE-2026-114938 a lower severity of 8.1 High under CVSS 3.1. Calif’s score uses CVSS 4.0, while Oracle’s rating uses CVSS 3.1.

Calif demonstrated unauthenticated remote code execution against default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate.

Calif also demonstrated remote code execution in sample applications built with Apache Struts and Spring Boot. Researcher samczsun showed that a Java program opening a TLS connection to a malicious server can be compromised without exposing its own service.

Calif demonstrated authenticated remote code execution against Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, and Spinnaker. Specially crafted Base64 input of 64 letter-A characters followed by one equals sign triggers memory corruption on newer affected versions. Older OpenJDK 17 versions require 128 letter-A characters followed by an equals sign to trigger the same corruption.

Calif published a proof-of-concept showing memory corruption but has not released weaponized exploits against specific enterprise applications. Calif said every target requires a custom profile with a decoder route and a suitable heap layout, meaning no universal exploit payload exists. OpenJDK HotSpot contains hand-written x86-64 assembly that accelerates Base64 decoding using AVX-512 VBMI instructions and bypasses normal Java memory safeguards.

Cisco Talos has not observed in-the-wild exploitation of CVE-2026-114938 as of November 18, 2026. Cisco Talos said, “Talos has not observed in-the-wild exploitation of this vulnerability yet.”

CyberScoop reported no exploitation in the wild as of its November 17, 2026 publication. CyberScoop said none of the related CVEs were on CISA’s Known Exploited Vulnerability list. CISA published a notice on November 17, 2026 calling for a patch.

A person in a blue blazer holding a white sheet displaying a full-year calendar grid.
A person holding a calendar sheet, representing key dates and deadlines for software updates. Photo by geralt on Pixabay

Calif researcher Quang Luong discovered the flaw using OpenAI’s Codex AI coding assistant during an OpenJDK audit. Luong needed about one hour to discover the flaw and another two hours for an initial working exploit at total AI cost under $200. Calif credited Quang Luong and Albert Yang for CVE-2026-114938 in Oracle’s November advisory. According to Calif, AI agents developed most exploit chains almost independently once researcher Quang Luong selected targets and provided exploitation knowledge.

Heise said on November 17, 2026 that unconfirmed information indicates the Base64 decoder flaw can be exploited starting with OpenJDK 17.0.6. Heise also suggested the issue may have existed since early 2023.

Oracle released patches for CVE-2026-114938 on November 17, 2026 as part of its November Critical Security Patch Update. OpenJDK published a security advisory on November 17, 2026. Oracle’s JDK 17.0.21.1 release notes carry the November 17, 2026 release date and link the security fixes to its November advisory.

Patched Oracle Java SE versions include 21.0.13.1, 25.0.5.1, and 27.0.1.1, according to an Aikido summary cited by calif.io. Rapid7 stated on November 17, 2026, “These CVE-specific details remain preliminary, pending confirmation in Oracle or OpenJDK advisories.”

Java powers enterprise applications, web services, financial systems, and critical business infrastructure worldwide. By Calif’s count, OpenJDK runs at 90% of Fortune 500 companies. Gal Elbaz, co-founder and CTO of Oligo Security, said, “We’re talking about a vulnerability in one of the most widely used software runtimes in the world.”

Cisco Talos SNORT SIDs 1:67502 through 1:67513 for Snort2 flag malformed encoded data in certain HTTP request fields. Cisco Talos SNORT SIDs 1:301754 plus 1:67502 through 1:67513 for Snort3 flag malformed encoded data in certain HTTP request fields.

Apply the software update for CVE-2026-114938, Cisco Talos recommends. Calif said those unable to update immediately can start OpenJDK with -XX:-UseBASE64Intrinsics as a temporary mitigation. Using -XX:UseAVX=2 disables AVX-512 instructions on x86-64 systems, while ARM-based processors do not recognize the flag and may fail to start.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *