OpenJDK · CVE-2026-114938
Java4Shell
Patch now if…Only on newer Intel/AMD CPUs.
A bug in Java's Base64 decoder can let an attacker run code on your server. It only works on newer Intel/AMD CPUs, so on most systems a two-command check settles whether you need to rush. Proof-of-concept code for the memory corruption is public, but no attacks are reported.
How scary is it?
Are you affected? only if all are true
1Java 17.0.6+, 21, 25 or 27command
Any distribution (Oracle, Temurin, Corretto, Zulu, Red Hat…) without the November 2026 fix, plus Oracle's Java 8 Performance Pack (8u511b33-perf) and Oracle GraalVM for JDK 17/21. Standard Java 8 and 11 aren't affected.11,2,8,10,17
java -version2CPU has AVX-512 VBMIcommand
Intel Ice Lake or newer, AMD Zen 4 or newer (including Ryzen). ARM servers (Graviton, Ampere) never are. Run it where the app runs, on every node pool, because clusters often mix CPU generations.1,2
grep -o -m1 avx512vbmi /proc/cpuinfo3Untrusted input gets Base64-decoded
Auth headers, tokens, SAML and uploads all qualify. Assume yes for anything internet-facing; researchers showed it against Jira, Confluence, Artifactory and Jenkins.7,9
What to do
1Patch Java
Oracle: 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 (17 Nov). Corretto shipped all four lines on 17 Nov. Temurin's fixed builds are out for x64 Linux, Alpine and Apple-silicon Macs, but on 20 Nov not yet for Windows or the eclipse-temurin Docker images. Red Hat, Ubuntu and Debian have fixed packages. For Oracle's Java 8 Performance Pack, see Oracle's advisory.16,15,13,14,12,18,19,11
Latest safe versions checked 20 Nov
2Can't patch yet? Set this flagcommand
Turns off only the vulnerable fast path. Needs a restart. Not an official Oracle workaround.8,3
-XX:-UseBASE64Intrinsics3Check bundled Java
Common tools like Jira, Confluence, Artifactory, Jenkins and many others ship with their own Java. Updating the system Java doesn't fix them: update the tool, or set the flag in its own JVM settings. Red Hat still lists its Keycloak build, JBoss EAP OpenJDK 17 images and OpenShift Pipelines as affected. Appliances too: Cisco (for example Catalyst Center and Finesse) and Palo Alto (Privilege Threat Analytics, Remote Access Connector, the on-prem HTML5 Gateway) list affected products, and Fortinet is still checking. Their firewalls (Cisco ASA/FTD, PAN-OS, FortiOS) aren't affected.7,9,12,20,21,22
This page shows you how to check. It can't tell you you're safe.
Sources (23) and changelog
- Calif: original disclosure 17 Nov
- Wiz: CPU check, workarounds
- Sophos: no attacks seen 18 Nov
- Qualys: fixed builds
- Orca: early doubts about Oracle's release notes
- Sonatype: version range unconfirmed
- SOC Prime: products demonstrated
- TuxCare: workaround
- CISA: patch-now alert 17 Nov
- Field Effect: Java 8/11 not affected
- CVE record (Oracle): affected and fixed Oracle builds
- Red Hat: CVE page, RHEL fixes 18–19 Nov 19 Nov
- Adoptium: Temurin November release includes the fix 18 Nov
- Adoptium: Temurin publishing status per platform 19 Nov
- Corretto 21.0.13.1.2 changelog: lists the CVE 17 Nov
- Oracle: JDK 17.0.21.1 release notes 17 Nov
- OpenJDK Vulnerability Group: advisory, affects 17, 21, 25, 27 17 Nov
- Ubuntu: fixed openjdk packages
- Debian tracker: fixed openjdk packages
- Cisco: affected products, PoC code public, no malicious use 19 Nov
- Palo Alto Networks: affected products and fixes, PAN-OS not affected 19 Nov
- Fortinet FG-IR-26-278: still investigating, FortiOS not affected 19 Nov
- Cisco Talos: no exploitation seen yet
- Cisco, Palo Alto and Fortinet appliance advisories added; PoC code for the memory corruption is public; Temurin Windows and Docker images still pending.
- Corretto, Ubuntu and Debian fixes out; Temurin Windows and Docker images still pending. Oracle fixed builds now cited to Oracle. Safe versions added.
- Review: Oracle's own fixed builds, Red Hat and Temurin fixes, GraalVM; 'disputed' note removed.
- Added the CISA alert and Oracle's Java 8 Performance Pack exception.
- Added fix status.
- Published.