java4shell: OpenJDK Base64 decoder flaw allows remote code execution on AVX-512 VBMI CPUs
On 17 November 2026, Oracle and OpenJDK published fixes for CVE-2026-114938, dubbed java4shell, which enables remote code execution and denial of service on x86-64 processors that support AVX-512 VBMI. CERT-FR issued an alert because OpenJDK underpins many widely deployed products, including Jira, Confluence, Jenkins, Keycloak, Kafka and Elasticsearch.
What to do now
- Product
- Oracle Java SE / OpenJDK
- Affected versions
- Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3; GraalVM for JDK 17.0.21.0.3, 21.0.13.0.3; GraalVM EE 21.3.20.0.3
- CVE
- CVE-2026-114938
France's CERT-FR published alert CERTFR-2026-ALE-016 on 18 November 2026 about CVE-2026-114938, a vulnerability nicknamed java4shell. The bug sits in OpenJDK's Base64 decoder and only affects x86-64 processors that support the AVX-512 VBMI instruction set. Oracle and the OpenJDK project released their own security advisories the day before.
According to the alert, a remote attacker can use the flaw to run arbitrary code or cause a denial of service. The attacker has to pass base64-encoded data to the APIs of the vulnerable component, and untrusted Java Web Start applications or applets play no part in this. Because each affected product needs its own tailored payload, exploitation is not generic. CERT-FR still urges vigilance.
The vulnerable versions listed are 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 Oracle GraalVM Enterprise Edition 21.3.20.0.3. CERT-FR notes that OpenJDK ships inside many products, including Keycloak, Atlassian Jira and Confluence, JFrog Artifactory, Jenkins, PingFederate, the Apache Kafka broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. The alert does not say whether exploitation has been seen in the wild.
Only CPUs with AVX-512 VBMI are exposed. On Linux, administrators can check this with the command CERT-FR provides, which filters the processor flags in /proc/cpuinfo: grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'. A host is in scope if the output lists all four flags: avx512f, avx512bw, avx512vbmi and bmi2.
Fixes are available through the Oracle and OpenJDK advisories, but the alert does not name the patched version numbers. Until updates can be deployed, the researcher who found the flaw recommends starting the JVM with the options -XX:-UseBASE64Intrinsics and -XX:UseAVX=2. These options turn off the vulnerable code path.
What to do now
- Apply the fixes referenced in the Oracle and OpenJDK security advisories of 17 November 2026 to every affected Java SE and GraalVM installation.
- Inventory applications that bundle OpenJDK, such as Jira, Confluence, Jenkins, Keycloak, Kafka, Solr or Elasticsearch, and check with each vendor for updated releases.
- Run CERT-FR's check command on Linux servers to see whether all four flags are present: avx512f, avx512bw, avx512vbmi and bmi2.
- Where patching must wait, start the JVM with -XX:-UseBASE64Intrinsics and -XX:UseAVX=2 on the affected hosts.