Java4Shell: vendors confirm the OpenJDK Base64 fix and who is not at risk
The OpenJDK patch reroutes short final Base64 groups to the safe decoder. Red Hat says ARM64 and non AVX-512 x86-64 are not exposed. No attacks seen yet, so patch internet-facing Java now.
By Junglewise News Desk. Published . Updated
The picture around the Java Base64 flaw nicknamed Java4Shell has become clearer, and for many small businesses the news is narrowing. Red Hat has confirmed that the bug does not expose ARM64 servers or x86-64 machines whose processors lack a feature called AVX-512 VBMI, according to Rapid7, which also reports Red Hat identifying OpenJDK 17.0.6 as the earliest affected version of Java 17. If your Java servers run on ARM, or on older Intel or AMD chips, you are very likely out of scope.
Everyone else should still treat this as a patch-this-week job. The flaw, CVE-2026-114938, lets someone send specially shaped text to a Java application and corrupt its memory, which in the worst case leads to running code on your server without logging in. Oracle shipped fixed builds on November 17 and the OpenJDK project published its own advisory the same day.
Rapid7 has also described what the official fix actually does: final Base64 groups shorter than four bytes are now handed to the ordinary Java decoder instead of the fast, hand-written routine that contained the bug. That is useful to know because it explains why the two unofficial mitigations circulating (switches that turn off the fast routine) are described as keeping the vulnerable code from running, even though neither Oracle nor OpenJDK lists them as supported workarounds and Sophos says it has not validated the Base64 intrinsics flag.
No exploitation has been seen in the wild. Sophos said in its advisory, published November 18, that it is not aware of any public reports of attacks, Cisco Talos said it has not observed exploitation but anticipates probing attempts may pick up after disclosure, and the CVE is not in CISA's Known Exploited Vulnerabilities (KEV) catalog, the US government list of flaws confirmed to be under attack. The US Cybersecurity and Infrastructure Security Agency, with input from the Canadian Centre for Cyber Security, urged organisations to patch immediately regardless.
For most small IT teams the hard part is not patching, it is finding the Java runtimes you did not know you had. Appliances, build servers and container images often bundle their own copy of Java that never appears in a software inventory.
What to do now
- Find your Java. CISA recommends hunting down every Java installation, including copies inside third-party applications, containers and appliances that will not show up as separate inventory entries. Check the running process, not just the system JDK.
- Check the processor. On Linux, according to Calif, a host only qualifies if the CPU reports all four flags:
avx512f,avx512bw,avx512vbmiandbmi2. Sophos suggests looking for theavx512vbmiflag as the quick test. ARM64 is not affected. - Patch. Oracle released fixed builds on November 17: Java 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1, and Java 8 Enterprise Performance Pack 8u513-perf. GraalVM for JDK moved to 17.0.21.1 and 21.0.13.1, and GraalVM Enterprise Edition to 21.3.20.1. CISA recommends reviewing Oracle's Critical Security Patch Update advisory for the full product list. Do internet-facing systems first.
- If you use another Java distribution, follow its own schedule. Amazon Corretto, Azul Zulu, Microsoft Build of OpenJDK, Eclipse Temurin, BellSoft Liberica, SAP SapMachine and Red Hat's OpenJDK build each ship fixes on their own timelines. Endor Labs said the fix had not yet reached the public OpenJDK update repositories for 17, 21 and 25 on November 17. Do not assume Oracle's version numbers apply.
- Prioritise by what the app does. Sophos advises starting with applications that decode Base64 from untrusted sources, such as authentication headers, tokens or file uploads.
- Interim mitigation if you cannot patch yet. Starting the JVM with
-XX:-UseBASE64Intrinsicsdisables the affected routine; on x86-64 only,-XX:UseAVX=2avoids the AVX-512 path. Google Cloud suggests settingJDK_JAVA_OPTIONS="-XX:+IgnoreUnrecognizedVMOptions -XX:UseAVX=2"and redeploying workloads, which works without upgrading Java. Verify a running process withjcmd <PID> VM.flags -all. Oracle lists neither flag as supported, Sophos has not validated the first one and recommends testing before deployment, and an ARM64 JVM will fail to start with the AVX flag. Remove them once patched. - Tighten the input path. CISA recommends validating Base64 input at the application boundary, enforcing input size limits, and limiting unauthenticated access.
- Watch for signs. CISA suggests monitoring for unexpected JVM crashes, rogue runtimes and suspicious Java processes. Talos published Snort2 and Snort3 rules, including SIDs
1:67502-1:67513and1:301754, that look for malformed Base64 in HTTP request fields.
Technical details
CVE-2026-114938 is a heap-based buffer overflow (CWE-122) in HotSpot's x86-64 AVX-512 Base64 decode intrinsic, the hand-written processor instructions the JIT compiler substitutes for the Java decoding loop in java.util.Base64 once a method runs hot. When the input ends in a padded fragment shorter than a full block, the output-length calculation goes negative and the store mask is read as full width, writing 62 or 63 bytes past the destination array and corrupting the next heap object, Horizon3 reports. Java rejects the malformed input afterwards, but catching that exception does not undo the corruption, which may only surface later as a crash during garbage collection.
The OpenJDK fix routes final groups shorter than four bytes to the ordinary decoder. Rapid7 gives a plain example of how untrusted data reaches the code: a web service decoding HTTP Basic credentials before it checks the username and password.
Three conditions must all hold: an affected Java build, an x86-64 CPU with AVX-512 VBMI, and JVM settings that permit the optimizing compiler and the Base64 intrinsic. An affected version alone does not mean an application is exploitable.
Severity scores differ. Oracle rates it CVSS 3.1 8.1 High, vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Calif, the firm that found the bug, rates it 9.2 Critical under CVSS 4.0, as does Cisco Talos.
Affected: OpenJDK 17.0.6 and later, including 21.x, 25.x and 27.x, and Eclipse Temurin 17.0.6 and later. Oracle Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3, Oracle GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, and GraalVM Enterprise Edition 21.3.20.0.3, with earlier versions likely affected. Not affected: standard Java 8 and 11, OpenJDK 17.0.0 to 17.0.5, ARM64, and x86-64 CPUs without AVX-512 VBMI. Google Cloud's bulletin says Java workloads on Kubernetes Engine, Cloud Run and App Engine may be exposed.
Calif says its initial testing achieved pre-authentication code execution in Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins and PingFederate in default configurations, and post-authentication execution in Apache Kafka Broker, Solr, Elasticsearch, Gerrit and Spinnaker. It describes a second technique it calls JavaBleed that reads application memory such as keys and tokens. Those are the researchers' own claims; Calif is withholding product-specific exploit chains, and its public proof of concept triggers the corruption without taking control.
How exploitable this is in practice is still unsettled. VulnCheck told SecurityWeek it built a full remote code execution exploit but does not expect wide exploitation, since it requires heap layout manipulation and target-specific work to defeat memory randomisation. Gal Elbaz, co-founder and CTO of Oligo Security, told CyberScoop that exploit development took hours but added: "That doesn't mean every Java application is vulnerable or that exploitation will be straightforward." Kevin Breen of Immersive said on November 17 that he had a working exploit needing per-application adaptation, a claim that has not been independently verified.
Oracle credits Quang Luong of Calif and Albert Yang with reporting the flaw. The CVE was reserved on October 22 and published November 17, alongside Oracle's Critical Security Patch Update containing 11 Java SE patches. Tenable, Cisco and Sophos all say they are still checking their own products for impact.
What changed
- : Added the OpenJDK fix detail routing short final Base64 groups to the standard decoder, Red Hat's confirmation that ARM64 and non AVX-512 chips are safe, and new Sophos, Rapid7 and Google Cloud guidance.
- : Added a researcher's claim of a working per-application exploit via Tomcat Basic auth and java-jwt, Oracle's credited reporters, and Java's history on CISA's exploited list.