News Vulnerabilities & Zero-Days
Java4Shell: Base64 Decoder Overflow in OpenJDK Is Reachable Before Authentication
Research firm Calif disclosed CVE-2026-114938, a heap overflow in the OpenJDK Base64 decoder path that uses AVX-512 VBMI instructions, and Oracle has shipped fixes. Calif claims pre-authentication code execution against several widely deployed Java products. No exploitation in the wild has been reported.

Key takeaways
- CVE-2026-114938 is a heap overflow in the OpenJDK Base64 decoder intrinsic that uses AVX-512 VBMI.
- Java servers often decode attacker-supplied Base64 before authentication, per The Hacker News.
- Calif claims pre-auth code execution in six named products and is withholding those exploit chains.
- The Canadian Centre for Cyber Security says it is not aware of active exploitation.
- Inventory JDK builds and CPU flags, then patch or apply a JVM flag workaround.
Research firm Calif has disclosed CVE-2026-114938, which it calls Java4Shell: a memory corruption flaw in OpenJDK's Base64 decoder. The bug is in the x86-64 intrinsic that uses AVX-512 VBMI instructions. Malformed input can make it write past the end of a heap array. Oracle has released patches, and OpenJDK published a security advisory alongside them.
The Canadian Centre for Cyber Security issued an alert classing the flaw as a heap-based buffer overflow (CWE-122). The alert says it is remotely exploitable without authentication by sending crafted Base64 data to a Java process on an affected processor.
Why this reaches applications with no bug of their own #
As The Hacker News notes, Java servers often decode attacker-supplied Base64 before they authenticate anyone: Basic auth headers, tokens, SAML artifacts. That puts the vulnerable code path in front of the login check. Exposure depends on the JDK build and the CPU underneath it, not on anything in your application code.
Who is affected #
Per Calif, the flaw affects a long run of recent OpenJDK builds, and only on x86-64 processors with AVX-512 VBMI. Calif lists Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4 or newer. ARM64 is not affected. The Cyber Centre alert lists the affected and fixed Oracle Java SE and GraalVM builds.
Claimed versus reproduced #
Keep these apart when you triage:
- Calif's claim: it achieved pre-authentication remote code execution in default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. It also reports post-authentication code execution in Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker, and calls the list non-exhaustive.
- What is public: Calif published a write-up and a self-contained proof of concept. It is withholding the application-specific exploit chains until users have had a chance to upgrade.
- Independent results: The Hacker News reports that other labs reproduced crashes and a memory leak, but not code execution.
- In the wild: the Cyber Centre says it is not aware of active exploitation, and adds that this can change quickly.
What to do #
- Check CPU flags on Java hosts, for example
lscpu | grep avx512. - Inventory JDK builds, including the runtimes bundled inside containers and vendor appliances.
- Patch to a fixed build from your JDK vendor.
- Where you cannot patch yet, apply a JVM flag.
-XX:UseAVX=2disables AVX-512 in the JVM, per both the Cyber Centre and Calif.-XX:-UseBASE64Intrinsicsdisables the hardware-accelerated Base64 path, per Calif.
One caution from Calif: use -XX:UseAVX=2 only on x86-64. OpenJDK on ARM will fail to start with it, so do not push that flag fleet-wide without checking architecture first.
Sources
- Java4Shell: Write once, RCE everywhere, Calif
- AL26-029 - Critical vulnerability impacting Oracle Java - CVE-2026-114938 - Canadian Centre for Cyber Security, Canadian Centre for Cyber Security
- Java4Shell Flaw (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak and More, The Hacker News
Questions this raises
- Is Java4Shell being exploited in the wild?
- No exploitation has been reported. The Canadian Centre for Cyber Security says it is not aware of active exploitation, and notes that this can change quickly.
- Are ARM servers affected?
- No. Calif says the flaw is in the x86-64 intrinsic that uses AVX-512 VBMI instructions, and that ARM64 is not affected.
- What can I do if I cannot patch the JDK right away?
- The Cyber Centre and Calif both list -XX:UseAVX=2, which disables AVX-512 in the JVM. Calif also lists -XX:-UseBASE64Intrinsics. Calif warns that -XX:UseAVX=2 must only be used on x86-64, because OpenJDK on ARM will fail to start with it.