Oracle has patched Java4Shell (CVE-2026-114938), a critical flaw in Java's Base64 decoder that allows unauthenticated remote code execution in Jira, Confluence, Jenkins or Keycloak. It affects x86-64 servers with AVX-512 VBMI running Java 17.0.6 or later. Inventory where Java runs, update and restart, starting with anything exposed to the Internet.
Key facts
- CVE-2026-114938 is a memory corruption bug in the HotSpot JVM's hardware-accelerated Base64 decoding. Calif rates it 9.2 in CVSS 4.0; Oracle gives it 8.1 in CVSS 3.1, with high attack complexity and no authentication required (BleepingComputer).
- It affects OpenJDK from 17.0.6 onwards and Java 21, 25 and 27, plus the distributions built on it: Oracle Java SE, Corretto, Temurin, Zulu, Red Hat and Microsoft. Standard Java 8 and 11 don't contain the vulnerable code; the Java SE 8 Performance Pack build 8u511b33-perf does.
- It only triggers on x86-64 CPUs with AVX-512 VBMI, such as Intel Xeon from Ice Lake onwards and AMD Zen 4 or later. ARM64 is not vulnerable.
- Fixed Oracle Java SE versions: 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. For Java 8 Performance Pack, 8u513.
- INCIBE-CERT published advisory INCIBE-2026-910, rated critical, on 18 November. Oracle's November update includes 655 patches for 640 vulnerabilities.
Am I affected if I use Jira, Jenkins or Keycloak?
If you host them yourself, probably yes. Calif researchers achieved unauthenticated remote code execution in Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate with default configuration (The Hacker News). With credentials, they also got it in Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. Those lists aren't exhaustive: any Java application on an affected server is a candidate, including custom-built apps and third-party software that ships its own Java.
You need two things at once to be exposed: an affected Java version and an x86-64 CPU with AVX-512 VBMI. If either is missing, that machine isn't vulnerable.
Watch your containers. Keycloak's x86-64 images tagged 26.8.2-1 and 26.8.2-2 ship an affected OpenJDK 21.0.13 (SecurityWeek). Keycloak has published temporary mitigations.
What if my vendor doesn't have a patch yet?
Oracle has released its builds; so have Corretto and Zulu. Red Hat was preparing its own. According to Endor Labs, as of 17 November the fix was not yet in the public OpenJDK 17, 21 and 25 update repositories (SecurityWeek). If you use another distribution, you depend on your vendor shipping a fixed build.
In the meantime you have two options. -XX:-UseBASE64Intrinsics disables only the vulnerable Base64 code. -XX:UseAVX=2 disables AVX-512 entirely and only applies on x86-64. Either way, you must restart services and rebuild container images.
Is it being exploited?
Not confirmed, according to INCIBE and The Hacker News. VulnCheck explains that crashing the JVM is easy, but achieving remote code execution requires target-specific work. Calif has released a proof of concept that only demonstrates the memory corruption and withholds the full exploit chains (BleepingComputer). Cisco Talos expects probing attempts to rise after public disclosure. CISA urged on 17 November to patch immediately and prioritise Internet-facing systems.
What to do today
- Inventory where Java runs: servers, VPS, containers, appliances and third-party products with embedded Java.
- Check each server's CPU. If it's ARM64 or lacks AVX-512 VBMI, that machine isn't vulnerable.
- Prioritise by exposure: Internet-facing systems first, such as Jira, Confluence, Keycloak or Jenkins.
- Update to the fixed builds, restart services and rebuild container images.
- If your distribution has no fixed build yet, start the JVM with
-XX:-UseBASE64Intrinsicsand note to remove it once you patch. - Ask your SaaS and custom software vendors, in writing, to confirm whether they run affected Java and when they'll patch.
What it means for a small business
Your risk comes down to two questions you can answer in a morning: which Java do you run, and on which CPU? Patching is the easy part. The hard part is the inventory, because Java turns up where nobody looks: inside a product you bought, in a container image nobody has rebuilt in months, on the server set up by someone who has since left.
Our advice is not to wait for a public exploit. There's no confirmed exploitation today, which gives you room to act in an orderly way, but the window will be short if the full chains are released. If you fall under NIS2, this work belongs in your vulnerability and supply chain management: keep a record of the inventory, patch dates and vendor responses.
If your team doesn't have time to do that inventory this week, it's the kind of work we cover in cybersecurity.
Frequently asked questions
Am I safe if I use Java 8 or 11?
The standard versions don't contain the vulnerable code. The exception is Java SE 8 Performance Pack 8u511b33-perf, fixed in 8u513.
Are my ARM servers affected?
No. The flaw only triggers on x86-64 CPUs with AVX-512 VBMI.
Is installing the new Java version enough?
No. You need to restart services and rebuild container images; otherwise the vulnerable version keeps running.
Sources
- CISA – Critical Java Vulnerability Requires Immediate Patching
- INCIBE-CERT – Múltiples vulnerabilidades en productos de Oracle (Java4Shell)
- BleepingComputer – Critical Java4Shell flaw allows RCE attacks on major Java applications
- The Hacker News – Java4Shell Flaw (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak and More
- SecurityWeek – Java4Shell Vulnerability Puts Many Enterprise Applications at Risk of Takeover