Daily Tech Now

Daily News on AI, Big Tech, Linux, Security & Gadgets

Java4Shell Vulnerability Hits AVX-512 Servers as Oracle Patches 11 Java Flaws

A 65-character Base64 string can corrupt memory inside Java on many modern Intel Xeon and AMD servers. Security firm Calif calls the flaw Java4Shell. It says the bug gave it remote code execution, with no login, in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. Oracle shipped fixes on November 17, 2026, together with 10 other…

Java4Shell vulnerability in the OpenJDK Base64 decoder on AVX-512 Java servers, fixed in Oracle's November 2026 Java patch

A 65-character Base64 string can corrupt memory inside Java on many modern Intel Xeon and AMD servers. Security firm Calif calls the flaw Java4Shell. It says the bug gave it remote code execution, with no login, in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. Oracle shipped fixes on November 17, 2026, together with 10 other Java security patches that have drawn far less attention.

The bug is tracked as CVE-2026-114938. Calif’s Java4Shell technical write-up rates it 9.2 out of 10 under CVSS 4.0. Oracle’s November 2026 Critical Security Patch Update advisory scores it 8.1 under the older CVSS 3.1 scale. Both agree that an attacker needs no credentials.

What Java4Shell is

Memory safety is one of Java’s main selling points, so developers rarely think about memory corruption. Calif points out that much of Java itself is written in C, C++ and assembly. The flaw sits in one of those low-level parts. It is an assembly routine that speeds up Base64 decoding with AVX-512 VBMI instructions on x86-64 chips.

This fast path mishandles the “=” padding character at the end of a Base64 string. The decoder then writes data past the end of its output buffer. It does throw an error afterwards, but nearby objects in memory may already be damaged by then.

Calif says the bug can also leak heap memory before any code runs. That leak could expose personal data, private keys, secret keys and tokens. Calif calls this part “JavaBleed.”

The technical details

The trigger is 64 letter “A” characters followed by one “=”. Java sets aside a 50-byte buffer for the decoded result. The padding logic pushes the output length below zero, to -1 or -2. A bit-masking step then leaves the store mask set to all ones, so the routine writes a full 64 bytes.

That write starts at offset 48 of the 50-byte array. As a result, 62 bytes land past the end. Calif says the attacker fully controls the first byte and partly controls the second, while bytes 48 to 63 always get the value 0x9a. Older OpenJDK 17 builds need 128 “A” characters instead of 64.

Which systems are affected

Calif and Oracle describe three conditions that must all apply:

  • Java version: OpenJDK 17.0.6 and newer, per Calif. That includes Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, BellSoft Liberica, SAP SapMachine, Red Hat OpenJDK and Oracle builds. Oracle lists 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. It also lists GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3, plus GraalVM Enterprise Edition 21.3.20.0.3.
  • Processor: an x86-64 CPU with AVX-512 VBMI. Calif names Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids. It also names AMD EPYC and Ryzen chips on Zen 4 or newer. ARM64 chips are not affected.
  • Input path: Oracle says the flaw can be exploited only by supplying data to APIs in the affected component, for example through a web service.

Calif tested default setups. Without logging in, it reached code execution in Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. With an account, it did the same in Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker. Sample apps built on Apache Struts and Spring Boot were also exploited. Calif says both lists are incomplete.

The attack is not one-size-fits-all. Calif says there is no universal payload, and each application needs its own exploit profile. Its researchers shaped memory remotely over the network, which worked best with short, stable delays. For one test, they rented a virtual machine in the same region as the target. Calif adds that nginx request buffering did not stop its Elasticsearch chain, because WebSocket frames skip that buffering.

Java clients are exposed too

Calif says researcher samczsun shared a separate client-side exploit with the firm. According to Calif, a Java program that opens a TLS connection to a malicious server “can be compromised, even if it exposes no service of its own.” The write-up does not say whether this client attack has the same CPU limits.

The other 10 Java fixes in Oracle’s update

Oracle’s advisory lists 11 new Java SE patches. It says all 11 may be remotely exploitable without authentication. Oracle’s own notes show that the risk to servers differs a lot between them. Some apply only to sandboxed clients that run untrusted code, such as Java Web Start apps or applets.

CVE Component CVSS 3.1 Who is exposed, per Oracle
CVE-2026-114938 (Java4Shell) Compiler (Multiple) 8.1 Apps that accept data through APIs, such as web services
CVE-2026-86144 JavaFX (libxml2) 7.5 Sandboxed clients running untrusted code only
CVE-2026-114939 JGSS 7.4 Sandboxed clients running untrusted code only
CVE-2026-114940 JSSE TLS 7.4 APIs such as web services, and sandboxed clients
CVE-2026-114941 Compiler 7.0 APIs such as web services
CVE-2026-114942 Libraries 7.0 APIs such as web services
CVE-2026-114943 Hotspot 6.5 APIs such as web services, and sandboxed clients
CVE-2026-114944 Core Java Libraries 5.9 APIs such as web services, and sandboxed clients
CVE-2026-114945 Libraries 5.3 APIs such as web services, and sandboxed clients
CVE-2026-114946 Compiler 4.8 APIs such as web services, and sandboxed clients
CVE-2026-114947 JSSE TLS 3.7 Sandboxed clients running untrusted code only

Version coverage also varies. CVE-2026-114941, -114942 and -114945 affect only the Java 21, 25 and 27 builds Oracle lists. CVE-2026-114947 affects only Java 25 and 27. CVE-2026-114939, -114940 and -114944 reach back to Java 8 and Java 11. The JavaFX patch also covers seven more libxml2 bugs, CVE-2026-86137 through CVE-2026-86143.

Oracle credits Java4Shell to Quang Luong of Calif and Albert Yang. It credits Nicholas Carlini of Anthropic for CVE-2026-114940, the TLS flaw in the JSSE component. The Java fixes are part of a much larger release, which Oracle says holds 655 new security patches across its product families.

Why it matters

Java4Shell needs a specific CPU, but the rest of the update does not appear to. Oracle’s advisory mentions no CPU condition for any of the 11 entries. A team running Java on ARM servers or older Intel chips is therefore outside Java4Shell’s reach, yet still exposed to flaws like CVE-2026-114940. Skipping the update because “our CPUs are not affected” would leave those holes open. Calif’s own advice is blunt: “All Java users should update immediately.”

For Java4Shell itself, the highest risk sits with servers that accept Base64 data from outside, since Oracle says the flaw is reached through data sent to APIs. Calif’s pre-login results cover identity systems such as Keycloak and PingFederate, along with widely used tools like Jira and Jenkins.

What to do now

  1. Update Java. Install Oracle’s November 17 builds or your vendor’s patched OpenJDK build. Oracle publishes the patch details in its support documentation, and other OpenJDK vendors ship their own fixed builds, so check each vendor’s advisory.
  2. Check your CPU on Linux. Calif suggests this command: grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'. A host is in Java4Shell’s CPU range only if all four flags appear.
  3. Use a stopgap if you cannot patch yet. Calif lists two JVM startup flags. -XX:-UseBASE64Intrinsics turns off the hardware-accelerated Base64 code. -XX:UseAVX=2 turns off AVX-512, but use it only on x86-64, because ARM builds of OpenJDK will not start with it. Security firm Horizon3.ai notes in its CVE-2026-114938 entry that Oracle does not publish either flag as a supported workaround.
  4. Start with exposed apps. Put internet-facing systems from Calif’s list first, especially the ones it broke without a login.
  5. Do not forget clients. Java programs that connect to outside servers over TLS also need the update, given Calif’s client-side exploit.

Exploits, AI and open questions

No attacks in the wild had been reported as of November 17, CyberScoop reported in its Java4Shell coverage. The flaw was also not on CISA’s Known Exploited Vulnerabilities list. Calif has published only a bounded test program that keeps every write inside a real array. It says “the weaponized chains for individual products stay private” until users have had a chance to upgrade.

Security firms Upwind and Sweet Security both say details of Java4Shell leaked before the patch was ready.

AI played a big part in the discovery. Calif says Quang Luong found the bug in about an hour using OpenAI’s Codex. A first working exploit took about two more hours, and total token costs stayed under $200. CyberScoop reports that Calif’s AI agents produced most of its exploit chains nearly on their own.

Several questions remain open. Calif has not said whether the client-side TLS attack depends on AVX-512 CPUs. The severity scores also differ, with 9.2 from Calif under CVSS 4.0 and 8.1 from Oracle under CVSS 3.1. Fixed build numbers for each OpenJDK distribution also have to be checked vendor by vendor.

About the Author

Trang Nguyen Avatar

Leave a Reply

Your email address will not be published. Required fields are marked *