Oracle and the OpenJDK project shipped fixes on November 17 for Java4Shell (CVE-2026-114938), a critical flaw in the Java runtime that researchers at Calif say lets an attacker with no login run code on servers running Keycloak, Atlassian Jira and Confluence, Jenkins, JFrog Artifactory and PingFederate in their default setups. Calif rates it 9.2 out of 10 under CVSS 4.0. Oracle scores it 8.1.

What’s new

According to Calif’s write-up, the bug sits in the hardware-accelerated Base64 decoder that OpenJDK uses on x86-64 processors with AVX-512 VBMI support. That covers Intel Xeon chips from Ice Lake onward and AMD Zen 4 or newer. ARM servers aren’t affected. Calif says a crafted Base64 string can corrupt memory, leak data and lead to remote code execution.

  • Affected: OpenJDK 17.0.6 and newer, plus builds made from it, including Oracle Java SE, Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK.
  • Fixed: Oracle patched it in its November 2026 Critical Security Patch Update, and OpenJDK published its own advisory the same day.
  • Exploits: BleepingComputer reports no attacks in the wild so far. Calif has published a proof of concept for the memory corruption but not its working exploits.

Who it affects

Most small business websites run on PHP, so a typical WordPress or WooCommerce site isn’t exposed through this bug. The risk sits with teams that self-host Java software: a Jira or Confluence Data Center server, a Jenkins build box, a Keycloak login server, or a search cluster on Elasticsearch or Solr. Atlassian Cloud and other hosted products are patched by the vendor.

Agencies and software teams that run their own CI or ticketing servers on modern x86 cloud machines should treat this as urgent.

Our take

Ask whoever manages your servers one question today: do we run Java anywhere, and on which CPU? If the answer is yes on a recent Intel or AMD server, update the Java runtime to the November patch level and restart the service. If you can’t patch this week, Calif’s stopgap is to start Java with the -XX:-UseBASE64Intrinsics flag. We’re checking client hosting and build servers for Java runtimes as part of this week’s patch round.

Need a hand with patching and server upkeep? Our website maintenance and IT consulting teams handle it. Read the original disclosure from Calif and Oracle’s November 2026 patch update.