Java4Shell is a memory bug in the code Java uses to decode Base64, the text encoding that carries login headers, tokens and file uploads. Calif, the firm that found it, ran code without a login on Keycloak, Jira, Confluence, Jenkins, Artifactory and PingFederate in their default setups.
Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.
There is a catch that shrinks the list. The broken code only runs on x86-64 processors with AVX-512 VBMI, which means recent Intel Xeon and AMD Zen 4 or newer chips. Oracle and OpenJDK shipped fixes on November 17, and CISA told organizations to patch right away.
The bug lives in Java itself, so the app on top of it can be fully patched and still exposed.
The 5-Minute Cyber BriefDon’t Miss the Policy Changes That Affect Security Decisions
Get the key CISA actions, new regulations, guidance, and risk shifts in a quick daily brief.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Oracle and OpenJDK fixed a Java4Shell flaw in the Base64 decoder
CVE-2026-114938 is an out-of-bounds write in the hardware-accelerated Base64 decoder of the HotSpot JVM. Oracle rates it 8.1 under CVSS 3.1 and marks attack complexity as high. Calif scores it 9.2 under CVSS 4.0.
OpenJDK lists Java 17, 21, 25 and 27 as affected, not Java 8 or 11. Calif says OpenJDK 17.0.6 and newer are affected, along with distributions built from it: Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK and Oracle Java SE.
On exploitation: Tenable reports that GreyNoise has seen exploitation attempts but no confirmed successful compromise on its sensors as of November 18. VulnCheck and a researcher at Immersive say they have working exploits; neither has released one. The flaw is not in CISA’s Known Exploited Vulnerabilities catalog.
Which Java servers are exposed to Java4Shell
Most companies don’t track Java as a product. It ships inside identity servers, build servers, ticketing tools and vendor appliances, and CISA warns those copies may not show up in a software inventory. A team that patched Jira last week can still be running a vulnerable JDK underneath it.
The hardware rule is the fastest filter. Calif lists Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, plus AMD EPYC and Ryzen on Zen 4 or newer. ARM64 servers are not affected. Cloud instances on those Intel and AMD generations count, so check the instance type, not just the data center.
Update Java to 17.0.21.1, 21.0.13.1 or later and restart
- Find every Java runtime on x86-64 hosts, including the ones bundled inside vendor products and container images. Start with internet-facing Keycloak, Jira, Confluence, Jenkins, Artifactory and PingFederate.
- Check the CPU. Calif’s command,
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$', must print all four flags for the host to be exposed. - Update to Oracle’s fixed builds (17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1) or your vendor’s matching OpenJDK build, then restart every JVM and rebuild container images. A JVM that keeps running still has the old code loaded.
- If a runtime can’t be updated today, Calif says starting it with
-XX:-UseBASE64Intrinsicsturns off the vulnerable code path.-XX:UseAVX=2also works on x86-64, but Java on ARM will refuse to start with it. - Ranking a list of Java apps by exposure is classic vulnerability triage; our CySA+ exam guide covers that skill.
Forward this
For whoever runs our servers and vendor appliances: a flaw in Java itself, called Java4Shell, lets attackers run code on apps such as Jira, Jenkins and Keycloak when the server has a recent Intel or AMD processor. Can someone list our Java-based systems, update Java on them to the November 17 builds and restart them? Vendor appliances may need the vendor’s own update.
Details
- CVE-2026-114938: memory corruption in the HotSpot compiler’s Base64 intrinsic (x86-64, AVX-512 VBMI). Published November 17, 2026. CVSS 3.1: 8.1 (Oracle, AC:H). NVD status: undergoing analysis.
- Fixed Oracle builds: Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1; 8u513-perf for the Java 8 Enterprise Performance Pack. GraalVM fixes are in Oracle’s November Critical Security Patch Update.
- Applications Calif exploited before login: Keycloak, Jira, Confluence, Artifactory, Jenkins, PingFederate. After login: Kafka broker, Solr, Elasticsearch, Gerrit, Spinnaker.
- CISA: alert of November 17, 2026 urging immediate patching. Not in the KEV catalog as of its November 18 update.
- Exploitation: attempts reported by GreyNoise, no confirmed compromise. Status: THEORETICAL.
Hunt / verify
- Look for unexpected JVM crashes since November 17 (hs_err_pid files, sudden service restarts) on internet-facing Java apps. A failed attempt usually crashes the JVM.
- Check web and proxy logs for unusually long Base64 values in Authorization headers, JWTs or upload fields aimed at your Java apps.
- After patching, run
java -versioninside each container and service account context to confirm the new build is the one actually running.
Source: CISA alert; Calif write-up
Sources
- CISA: Critical Java Vulnerability Requires Immediate Patching (November 17, 2026)
- Oracle: Critical Security Patch Update, November 2026
- OpenJDK Vulnerability Advisory: 2026/11/17
- Calif: Java4Shell, Write once, RCE everywhere
- Tenable: Java4Shell (CVE-2026-114938) FAQ
- NVD: CVE-2026-114938
- oss-security: CVE-2026-114938 thread
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.