JAVA4SHELL RESPONSE SHEET - CVE-2026-114938 Core advisories reviewed: 18 November 2026, 16:41 UTC. This is a dated snapshot. Current guide: https://java4shellguide.com/ Current vendor fixes: https://java4shellguide.com/reference#patches EXPOSURE CONDITIONS The flaw is in an accelerated decoder: a faster way Java processes Base64 text. The documented attack needs all three conditions below, with that shortcut enabled. 1. An unpatched Java release Unpatched OpenJDK 17.0.6 onwards, including 21, 25 and 27. Vendor products with backported decoder code can differ; see the Java 8/11 exceptions below. 2. Certain Intel or AMD processors The shortcut needs x86-64 with AVX-512 VBMI. Native ARM64 Java is outside this hardware scope. Use the processor features available to the service itself, including inside a virtual machine. 3. Attacker-supplied data reaches Java Login credentials, tokens and uploads may be decoded before a user signs in. A login screen alone is not protection. Java clients can also process hostile server data. Java 8 / 11: Standard OpenJDK 8 and 11 are not marked affected by this CVE. Oracle Java 8 Enterprise Performance Pack and Azul Prime (formerly Zing) are exceptions. Oracle lists 8u511b33-perf as affected; Prime has affected Java 8 and 11 builds. UPDATE AND VERIFY [ ] Find the Java runtime each service actually uses. Record vendor, full build, CPU features and owner. Include containers, CI agents, bundled JVMs and appliances. Prioritise internet-facing and login services. [ ] Patch, or apply the temporary JVM flag. Use a vendor-confirmed fix. If it is unavailable, set -XX:-UseBASE64Intrinsics in each affected service’s startup options. Test service health after the change. [ ] Restart and verify every instance. Rebuild images and roll out new containers where needed. Check the running JVM’s build and flags; installing a package does not replace an already-running process. [ ] Track exceptions and investigate suspicious activity. Record evidence and remaining owners. If compromise is suspected, preserve logs and follow your incident response process. Patching does not undo a compromise. TEMPORARY MITIGATION -XX:-UseBASE64Intrinsics This Java startup option turns off the affected fast decoder. Ordinary Base64 decoding still works. Add it to the app’s supported startup settings and restart. Check UseBASE64Intrinsics = false in the running Java process. Keep the permanent update planned. VERIFY THE RUNNING PROCESS jcmd VM.version jcmd VM.flags -all Use an available JDK tool with permission to inspect the service process, inside its host/VM/container. Replace with its process ID. IF YOU USE AN APP Installed app: follow the maker’s Java4Shell update advice, or your IT team’s instructions on a work device. Some apps include Java; updating a separate Java installation may not fix them. Online service: the provider must update its servers. Check its service notice or ask whether it has fixed CVE-2026-114938. Updating your browser cannot fix its servers. PRIMARY SOURCES Calif · original research https://calif.io/java4shell OpenJDK · 17 November advisory https://openjdk.org/groups/vulnerability/advisories/2026-11-17 Oracle · November security update https://www.oracle.com/security-alerts/cspunov2026.html Red Hat · Java4Shell bulletin https://access.redhat.com/security/vulnerabilities/RHSB-2026-018 Adoptium · Temurin patch guidance https://adoptium.net/news/2026/11/temurin-november-2026-cspu-java4shell Azul Prime · November CVE fixes https://docs.azul.com/prime/CVE-Fixes-November26 Published by After Dinner Software: https://afterdinnersoftware.com/