Java4Shell: Patch OpenJDK Base64 Flaw Now
Oracle shipped fixes on November 17 for CVE-2026-114938, a Base64 decoder memory-corruption bug in OpenJDK 17.0.6 and later. Here is what to patch first.

Patch your Java runtimes. Oracle released fixes on November 17 for CVE-2026-114938, a memory-corruption flaw in OpenJDK’s Base64 decoder that researchers have named Java4Shell, BleepingComputer reported. The fix shipped in Oracle’s November Critical Security Patch Update.
What changed
According to BleepingComputer, the bug sits in a hardware-accelerated Base64 decoding function. It can lead to disclosure of memory contents or remote code execution. It affects OpenJDK 17.0.6 and later, plus distributions built from the same code: Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK.
Two conditions limit who is exposed. The vulnerable path is only used on certain x86-64 processors with AVX-512 VBMI support. And there is no universal exploit: an attacker has to find an application-specific way to push crafted Base64 data into the decoder.
Calif, the firm that reported the flaw, says it demonstrated code execution against several widely used Java applications in default configurations, including Keycloak, Jira, Confluence, Jenkins, JFrog Artifactory and PingFederate. Calif has published a proof-of-concept for the memory corruption but not the weaponized chains. We are not describing the mechanics here.
Severity ratings differ by source, so treat any single number with care. Calif rated the flaw critical, while Oracle assigned a lower, High rating, per the same report. The Hacker News noted before the patch that the CVE record was still reserved and that early analyses by other firms pointed toward a JVM crash rather than code execution. That disagreement is a reason to patch, not to wait.
What to do
- Update the JDK or JRE. Oracle’s planned replacement builds are 8u513, 11.0.33.1, 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, according to The Hacker News. If you run another vendor’s build, take that vendor’s update for the same fix.
- Patch internet-facing Java apps first. Identity providers, CI servers, wiki and issue trackers, and artifact repositories come before internal batch jobs.
- Check your hardware. Hosts without AVX-512 VBMI are not on the affected decoding path, per the BleepingComputer report. That is a reason to order the work, not to skip it.
- Restart. A new JDK on disk does nothing for a JVM that is still running the old one.
- Watch for application vendor advisories. Bundled runtimes in products you run may need the vendor’s own update.
Priority call
Internet-facing apps on AVX-512 hardware go first. Everything else follows in your normal window, which should be days, not weeks, given that a PoC is public. Oracle’s wider November update also covers other Java SE flaws, and The Hacker News reports Oracle said all 11 may be exploited over a network without credentials, so the new builds are worth taking regardless.
Related: see the Oracle hub.
Found this useful? Share it.


