Java4Shell: Critical Java Flaw and What to Check Now
Admin
On 17 November 2026, Oracle and the OpenJDK project released patches for CVE-2026-114938, nicknamed "Java4Shell". It is a flaw in Java's Base64 decoder that, according to Calif, the security firm that found it, lets attackers run code without a password on Jenkins, Jira or Keycloak. It affects Java 17 and later on x86-64 processors with AVX-512.
What we know
- What it is: a memory-corruption bug in the hardware-accelerated Base64 decoder of Java's HotSpot virtual machine on x86-64, according to a CISA alert dated 17 November. Crafted Base64 input can crash the application or, in some cases, run code.
- Severity: the OpenJDK advisory scores it 8.1 out of 10 (CVSS 3.1). Calif rates it 9.2 under CVSS 4.0, and Red Hat classifies it as "Critical".
- Which versions: according to Calif, OpenJDK 17.0.6 and later. The OpenJDK advisory lists 17.0.21, 21.0.13, 25.0.5, 27.0.1 and earlier as affected. Red Hat says Java 8 and 11 are not known to be affected.
- Which processors: only x86-64 chips with the AVX-512 VBMI instruction set, such as Intel Xeon from Ice Lake onward or AMD Zen 4 and later, according to Calif. ARM64 processors are not affected.
- Which applications: Calif achieved code execution without credentials, in default configurations, on Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate. With a valid login, also on Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker. It says the list is not complete.
- Who found it: Quang Luong of Calif, using Codex, OpenAI's coding assistant. Calif says it took about an hour to find and two more hours to build the first working exploit, for under $200 of AI usage. Oracle also credits Albert Yang.
- Is it being exploited: Calif released only a proof of concept that shows the memory corruption and is holding back the application-specific exploits. Red Hat reports no attacks, and The Hacker News says there is no evidence of in-the-wild exploitation.
- What authorities ask: CISA, the US cybersecurity agency, urges immediate patching, starting with internet-facing systems, and asks organizations to look for Java bundled inside other applications, container images and appliances.
- The patch: it shipped on 17 November in Oracle's November security update, which contains 655 patches in total.
What changes and what doesn't
- WordPress and Drupal do not run on Java: they run on PHP, so the website itself does not have this flaw.
- What can run on Java around a website: internal search (Solr or Elasticsearch, used by modules such as Search API Solr for Drupal or plugins such as ElasticPress for WordPress), a Jenkins server that deploys changes, a Keycloak instance that handles logins, or self-hosted Jira and Confluence.
- Solr and Elasticsearch need a valid login for this attack, according to Calif. The risk is lower, but not zero if they are open to the internet or use default passwords.
- There is no universal exploit: according to BleepingComputer, an attacker needs an application-specific way to get the Base64 input to the decoder, which is why Calif tested app by app.
- If your server runs on ARM or on an x86-64 chip without AVX-512 VBMI, this flaw does not affect you, though the update fixes other issues and is still worth applying.
How to tell if you are affected
- List what runs on Java. On each server,
java -versionshows whether Java is installed and which version. CISA warns that Java can be bundled inside other applications, Docker images or appliances without showing up in your inventory. - Check the processor. On Linux,
grep -o avx512vbmi /proc/cpuinfo(the check Red Hat gives). If it returns nothing, that machine is not vulnerable to this flaw. - Update Java to the build your distribution released from 17 November onward: Eclipse Temurin, Amazon Corretto, Red Hat, Ubuntu or Oracle's JDK. If the application ships its own Java, as the Jenkins or Keycloak Docker images do, update the application.
- If you cannot update today, Calif and Red Hat give a temporary workaround: start the JVM with
-XX:UseAVX=2(x86-64 only; on ARM it stops the JVM from starting) or, per Calif, with-XX:-UseBASE64Intrinsics. Remove it once you patch. - Start with what faces the internet: the Keycloak login page, the Jenkins dashboard, Jira. In the meantime, CISA recommends limiting unauthenticated access, for example behind a VPN or an IP allowlist.
- If your site is on managed hosting, ask your provider whether its search or other services it runs for you use Java, and whether it has applied the 17 November patch.
- Watch for odd crashes: CISA asks defenders to look for unexpected JVM crashes and Java processes they do not recognize.
Related: Critical Linux Kernel Flaw: What to Check on Your Server
Sources
- OpenJDK, "OpenJDK Vulnerability Advisory: 2026/11/17"
- Oracle, "Critical Security Patch Update – November 2026", 17 November 2026
- CISA, "Critical Java Vulnerability Requires Immediate Patching", 17 November 2026
- Calif, "Java4Shell", 17 November 2026
- Red Hat, "RHSB-2026-018", 17 November 2026
- BleepingComputer, "Critical Java4Shell flaw allows RCE attacks on major Java applications", 17 November 2026
- The Hacker News, "CISA Urges Immediate Patching of Java4Shell Flaw That Could Allow Remote Code Execution", 18 November 2026
Updates: any changes backed by a primary source will be added here.
Worried about how this affects your website?
We will go over what to change with you. It is a free 30-minute call.