A flaw in Java’s Base64 decoder, nicknamed Java4Shell and tracked as CVE-2026-114938, can let an attacker corrupt the memory of a Java process and, in some applications, run code without logging in. The researchers at Calif disclosed it on November 17, 2026, CISA issued an alert the same day, and monitoring firms now report probing. As of November 18 no confirmed successful attack had been reported and the bug is not in CISA’s Known Exploited Vulnerabilities catalog, but a public proof of concept exists. Here is who is affected, which Java builds fix it, what to do if you cannot patch today and how to check your own servers.
What is Java4Shell (CVE-2026-114938)?
It is a heap buffer overflow in the x86-64 HotSpot JVM’s optimised Base64 decoder, which uses the AVX-512 VBMI processor instructions. When an application decodes a crafted Base64 value, such as a malformed login token, the decoder can write past the end of its buffer. Calif rates it 9.2 (Critical) on CVSS 4.0, while the OpenJDK advisory scores it 8.1 (High) on CVSS 3.1. The Hacker News reports the vulnerable code came from an OpenJDK change merged in June 2021, per Aikido’s analysis.
Who is affected?
Keycloak, which published a detailed advisory, says all three conditions must hold:
- An unpatched OpenJDK-based build from 17.0.6 onward, including unpatched 21 and 25 builds. Censys also lists 27 as affected in the OpenJDK advisory.
- An x86-64 host or virtual machine that exposes the
avx512vbmiCPU feature to Java. Censys names Intel Xeon Ice Lake and newer, and AMD Zen 4 and newer. ARM64 hosts are not affected, according to Calif. - A running JVM that has the Base64 intrinsics enabled, meaning it was not started with
-XX:UseAVX=2.
Java 8 and 11 are unclear. Censys notes that Oracle lists one Java 8 build as affected while Red Hat lists its Java 8 and 11 packages as not affected, so check your vendor’s advisory if you still run them.
Calif demonstrated unauthenticated code execution in test setups of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and execution after login on others such as Kafka, Solr and Elasticsearch, according to The Hacker News. Calif says there is no single universal exploit and has withheld product-specific chains. Wiz and VulnCheck reproduced parts of the attack, and VulnCheck says a full exploit has been available to its customers since the evening of November 17 (Censys).
Which Java builds fix it?
- OpenJDK: 17.0.21.1, 21.0.13.1 and 25.0.5.1 (Keycloak). Oracle released JDK 17.0.21.1 on November 17, though its release notes do not name the CVE (Censys).
- Amazon Corretto: 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2 and 27.0.1.1.4 (Censys).
- Eclipse Temurin: Linux builds are out and other platforms were still being built when Keycloak published.
- Red Hat: an advisory fixes the OpenJDK 25.0.5.1 portable Linux build, but Red Hat’s CVE page still showed Java 17, 21 and 25 packages as affected with no errata when Censys checked.
- Keycloak images: the 26.8 images were rebuilt on a fixed runtime. The tags to use are
latest,26.8,26.8.2and26.8.2-3. The tags26.8.2-1and26.8.2-2still bundle an affected build.
Keycloak warns not to trust a product version number alone, because images can bundle different Java runtimes and vendors may backport fixes. Confirm the runtime build.
How do you check whether a host is exposed?
On a Linux host, or the node that runs your container, Keycloak gives this check for the CPU feature:
grep -m1 '^flags' /proc/cpuinfo | grep -qw avx512vbmi && echo 'AVX-512 VBMI available'If nothing prints, that CPU is not known to be affected. Censys cautions that this is for prioritising, not for ruling hosts out, because workloads can move between processors. CISA also asks organisations to inventory Java runtimes bundled in third-party applications, container images and appliances, not only the JDK they installed themselves.
What if you cannot patch today?
- Turn off the Base64 intrinsics: start the JVM with
-XX:-UseBASE64Intrinsicsand restart every instance. Keycloak says Red Hat prefers this option for Keycloak. VulnCheck tested it with-XX:+UnlockDiagnosticVMOptionsin front and reported it stopped the overflow on OpenJDK 17, 21 and 25. Neither option was reported tested on OpenJDK 27, and no performance figures exist. Base64-heavy workloads may slow down. - Or limit the JVM to AVX2:
-XX:UseAVX=2. It should only be used on x86-64 hosts because it fails to start on ARM. - Verify the live JVM: Keycloak says to run
jcmdand look forUseBASE64Intrinsics = falseon every process after each restart. Seeing the option in an environment variable is not enough. - Reduce exposure: CISA suggests validating and restricting Base64 input at the application boundary, setting input-size limits and limiting unauthenticated access. These are partial protections, and a web application firewall may not cover every code path.
Neither flag replaces the patch. If an instance was exposed while unpatched, review it for signs of use and rotate credentials if you cannot rule out compromise.
Is it being exploited?
Not confirmed. Censys reports no confirmed successful exploitation as of November 18, but says monitoring providers see probing and exploit-shaped requests. The Hacker News adds that watchTowr has seen Java4Shell reconnaissance user agents and that Cloudflare and Previdian logged attempts from several IP addresses. Public GitHub repositories claim exploit chains against lab applications, though none is independently verified. We will see whether CISA adds it to KEV, which we track in our weekly Exploited This Week roundup. For another urgent infrastructure flaw, see our post on the VMware vCenter zero-day.
What is still unknown?
- Fixed builds for every Java distribution and platform. Several vendors had not shipped packages at the time of the sources.
- Whether Java 8 and 11 are affected in any build.
- How many internet-facing systems are vulnerable. Censys links search queries but gives no totals.
- Whether any in-the-wild attack has succeeded.
Sources
- Keycloak: Java4Shell, what Keycloak admins need to do (updated November 19, 2026)
- Censys advisory: OpenJDK remote code execution (Java4Shell)
- The Hacker News: CISA urges immediate patching of Java4Shell flaw
Image: Duke, the Java mascot, BSD licence, via Wikimedia Commons.
Like our coverage? Add stepphase.com as a preferred source on Google to see more of our stories in Top Stories.
