Security alert · High
Java4Shell: OpenJDK flaw CVE-2026-114938 allows remote code execution on AVX-512 servers
· 5 minutes read · Centoculus Security Team
Known since
Affected: OpenJDK 17.0.6 and newer and the Java distributions built on it (Oracle 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), only on x86-64 CPUs with AVX-512 VBMI
What happened
On 17 November 2026, Oracle and the OpenJDK project released fixes for CVE-2026-114938. The researchers at Calif.io, who found the bug, call it "Java4Shell". It is a memory-corruption bug in the optimised x86-64 code (a so-called intrinsic) that the HotSpot JIT compiler uses to decode Base64. After the decoder has been compiled to native code, malformed Base64 input can write past the end of the output array and overwrite neighbouring heap memory. A string of 64 A characters followed by a single = is enough to trigger it (128 A characters on older OpenJDK 17 builds). According to the researchers, the bug can leak heap memory, similar to Heartbleed, and can lead to remote code execution.
Oracle rates the bug CVSS 3.1 8.1 (high) and describes it as hard to exploit. No login is needed, and it can be reached over the network via multiple protocols, for example through a web service. The researchers give it 9.2 (critical) under CVSS 4.0.
In the default configuration, Calif demonstrated remote code execution without login in Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. They demonstrated it after login in Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. They say these lists are not complete. They also achieved code execution in sample applications built on Apache Struts and Spring Boot, through ordinary features such as authentication and file uploads. In addition, a Java program that opens a TLS connection to a malicious server can be compromised, even if it offers no service of its own.
Calif has published a proof of concept that triggers the bug but has not published its exploits for specific products. The researchers say there is no universal exploit, because each application needs its own exploit chain. CISA does not list the vulnerability in its catalogue of known exploited vulnerabilities, and no source we checked reports attacks so far.
Who is affected
All three conditions must apply:
- Java version: According to Calif, OpenJDK 17.0.6 and newer is affected, along with distributions built from it: Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK, Oracle OpenJDK, Oracle Java SE and Oracle GraalVM for JDK. Oracle lists these affected versions: 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; Oracle GraalVM Enterprise Edition 21.3.20.0.3. For Java 8, Oracle lists only the 8u511b33-perf build, not the standard 8u511b33 build, and it does not list Java 11 for this CVE.
- CPU: The vulnerable code only runs on x86-64 processors with AVX-512 VBMI. According to the researchers, that includes Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD EPYC and Ryzen from Zen 4 onwards. ARM64 servers are not affected. Servers with older x86-64 CPUs without AVX-512 VBMI are not affected either.
- Exposure: The application must pass data from outside to Java's Base64 decoder. According to Calif, this is the case in many common applications and frameworks in their default configuration.
Servers that run no Java applications are not affected. That includes typical PHP, Node.js or WordPress hosting.
What to do now
- List your Java runtimes. On every server, find out which Java runtime each application actually uses (
java -version, the start scripts and systemd units). Some applications ship their own Java runtime, so updating the system package does not always cover them. - Check the CPU. Run the command in the section below. On ARM64 or on CPUs without the four flags, this bug cannot be exploited. Update anyway with your next regular maintenance.
- Install the fixed Java version. Oracle released the fix in its Critical Security Patch Update of November 2026, and OpenJDK published its own advisory. The source data does not list exact fixed version numbers. Check the Oracle advisory linked below, plus the advisories from your Java vendor or Linux distribution (e.g. the Red Hat CVE page), and install their updated packages. For applications that ship their own Java runtime, install the vendor's updated release or point the application to an updated runtime.
- Restart all Java services. The new runtime only takes effect after a restart, for example Keycloak, Jenkins, Jira, Confluence, Artifactory, Solr, Elasticsearch, Kafka or Tomcat-based applications. Then check that the services start and respond normally.
- If you cannot update right away, use a workaround. Calif describes two JVM start options that block the vulnerable code path:
-XX:-UseBASE64Intrinsicsturns off hardware-accelerated Base64 encoding and decoding.-XX:UseAVX=2turns off AVX-512. Use this only on x86-64 hosts: OpenJDK on ARM does not recognise the option and will not start. Add the option to the application's JVM options (e.g.JAVA_OPTSor the service configuration) and restart the service. Note: the researchers say that request buffering in a reverse proxy such as nginx is not a general protection.
- Limit exposure. Until the update is installed, do not expose admin and login interfaces of Java applications (Jenkins, Keycloak admin, Jira, Artifactory) to the internet if they do not need to be.
How to check whether you are affected
Check whether the CPU has the required features. The output must include all four flags avx512f, avx512bw, avx512vbmi and bmi2:
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
If fewer than four flags appear, this bug cannot be exploited on the host.
Find running Java processes and their runtimes:
ps -eo pid,args | grep [j]ava
readlink -f /proc/<PID>/exe
/path/to/java -version
Compare the versions with the Oracle advisory and your vendor's advisory. Calif's write-up also includes a self-contained Java test program (Base64Trigger). Run with an affected runtime, it prints REPRODUCED. The researchers say it is safe to run because all writes stay inside a real array. Run it with the same Java binary and JVM options your application uses, before and after the update.
If an exploit attempt places memory wrongly, the JVM can crash. Calif notes that attackers can then simply try again. Unexpected JVM crashes (hs_err_pid*.log files in the working directory of the application) or unexplained restarts of Java services on affected hosts are worth a closer look.
Sources
- https://nvd.nist.gov/vuln/detail/CVE-2026-114938
- https://www.cisa.gov/news-events/alerts/2026/11/17/critical-java-vulnerability-requires-immediate-patching
More sources (7)
- https://www.oracle.com/security-alerts/cspunov2026.html
- https://access.redhat.com/security/cve/cve-2026-114938
- https://calif.io/java4shell
- https://github.com/Azure/azure-functions-java-worker/issues/909
- https://github.com/chainguard-dev/cg-skills/pull/17
- https://github.com/corretto/corretto-27/blob/27.0.1.1.4/CHANGELOG.md
- https://news.ycombinator.com/item?id=50538240
Related posts
Alerts ·
WordPress plugin vulnerabilities: 8 plugins, including WPvivid Backup
Vulnerabilities in eight WordPress plugins were disclosed on 20 November 2026, among them WPvivid Backup, NextGEN Gallery and Optimole. The most serious, in Mang Board, lets unauthenticated visitors delete board posts.
Alerts ·
Drupal core: critical installer flaw can allow site takeover without login
Drupal fixed a critical flaw in the built-in installer (install.php). Under specific conditions it lets attackers without a login reinstall a site and take it over. Update to 10.6.22, 11.3.22 or 11.4.13, and block the installer.
Alerts ·
VMware vCenter Server: critical authentication bypass fixed after zero-day attacks
Broadcom has fixed a critical authentication bypass in VMware vCenter Server (VMSA-2026-0009). Mandiant says it was used in zero-day attacks from early September 2026. vCenter 8.0, 9.0 and 9.1 are affected. ESX hosts are not.