How to tell if your Java servers are exposed to Java4Shell (CVE-2026-114938)

Cybersecurity

Quick answer: Java4Shell is a memory-corruption bug in how OpenJDK 17.0.6 and newer decode Base64 data. It only matters on x86-64 processors with AVX-512 VBMI; ARM systems are not affected. Calif disclosed it Nov 17, 2026, the same day Oracle and OpenJDK shipped patches. As of early Nov 19, GreyNoise had seen over 150 matching requests from five IP addresses and no successful intrusions on its sensors; WatchTowr and Cloudflare also report probing. Patch or apply a workaround flag, then restart. (SecurityWeek; Calif)

Am I affected?

You are exposed only if all of these are true (per Palo Alto Networks and Calif):

  1. Your Java runtime is an affected OpenJDK build. Palo Alto lists Java 17.0.6 through 17.0.21, Java 21 before 21.0.13.1, Java 25 before 25.0.5.1 and Java 27 before 27.0.1.1, plus some end-of-life versions. IBM Semeru is not affected, per the Quarkus team.
  2. Your CPU is x86-64 with AVX-512 VBMI. Calif names Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4 or newer.
  3. The Base64 shortcut is on. It is on by default. Starting the JVM with -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 turns the risky path off.
  4. Untrusted Base64 reaches your app. Almost any web app decodes Base64 in places like login headers or tokens. (Quarkus; Palo Alto)

How to check

  1. CPU: on Linux, run grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'. The host is in scope only if all four flags print. In a virtual machine, run it inside the VM. (Calif; Kai Labs)
  2. Running JVM, not just the installed package: use java -XX:+PrintFlagsFinal -version | grep -E 'UseBASE64Intrinsics|UseAVX' with the same binary and options as your service, or jcmd <pid> VM.flags -all. Bundled and containerized runtimes can differ from the one on your path. (Kai Labs)
  3. Vendor products: Cisco says more than a dozen of its products are affected and has no fixes or workarounds yet. Siemens says three Industrial Edge Management products are affected. Elastic says every Elasticsearch release from 7.17.3 onward is affected. Red Hat rates it Critical for RHEL 8, 9 and 10. (SecurityWeek)

What to do

  1. Patch. Install the November OpenJDK or Oracle update. Amazon, Microsoft and Azul have released patched OpenJDK builds. Restart services, because a patch only counts once the JVM restarts. (SecurityWeek; Calif)
  2. If you cannot patch yet, start the JVM with -XX:-UseBASE64Intrinsics, which Palo Alto recommends. It turns off only the vulnerable Base64 path and works on ARM too. -XX:UseAVX=2 also works but is x86-64 only and stops OpenJDK on ARM from starting, so do not push it through a shared base image. Remove the flag after patching. (Palo Alto; Calif)
  3. Atlassian Data Center: until patches arrive, Atlassian recommends disabling AVX-512 for Bamboo, Bitbucket, Confluence, Crowd, Jira and Jira Service Management. Atlassian cloud customers need to do nothing. (SecurityWeek)
  4. Keycloak and Jenkins: Keycloak’s 26.8.2-1 and 26.8.2-2 container images bundled a vulnerable OpenJDK 21; 26.8.2-3 has a patched runtime. Jenkins says update to the November Java releases and restart. (SecurityWeek)

What is still unknown

Whether anyone has been breached. GreyNoise saw no successful intrusions on its sensors and Previdian says its data cannot confirm compromises. WatchTowr says what it has seen is not particularly functional yet, but expects attackers to refine product-specific exploits over the coming days. A full exploit exists for VulnCheck customers, and Calif says it achieved remote code execution against default Jira, Confluence, Jenkins and Keycloak setups, each with its own tailored attack chain. No indicators of compromise are published in the sources we read. (SecurityWeek; Calif)

FAQ

Is this the same as Log4Shell? The name echoes it, but the cause differs: a memory bug in hardware-specific Base64 code, not a logging feature. (Calif)

Does it hit ARM servers, like AWS Graviton? No. ARM64 is not affected, but do not use the AVX flag there. (Calif)

Is it in CISA’s Known Exploited Vulnerabilities list? We did not see it in CISA’s Nov 18 additions. Check CISA’s catalog for updates.

Sources

AltTab Dad