---
title: "Java4Shell flaw in Java’s Base64 decoder lets attackers corrupt server memory; US cyber agency urges patching"
url: https://badiyaa.com/java4shell-cve-2026-114938-java-base64/
published: 2026-11-19T11:57:00+00:00
modified: 2026-11-19T11:57:00+00:00
section: Tech
publisher: Badiyaa
---

# Java4Shell flaw in Java’s Base64 decoder lets attackers corrupt server memory; US cyber agency urges patching

Java4Shell (CVE-2026-114938) is a memory bug in Java's Base64 decoder on AVX-512 servers; CISA told organizations to patch Java immediately.

Sixty-four letter A’s followed by a single equals sign are enough to corrupt memory inside Java on many modern servers. That is the trigger for Java4Shell, a flaw tracked as CVE-2026-114938, and the US Cybersecurity and Infrastructure Security Agency told organizations on November 17 to patch it immediately.

In [CISA’s alert on the Java vulnerability](https://www.cisa.gov/news-events/alerts/2026/11/17/critical-java-vulnerability-requires-immediate-patching), the agency describes a critical memory-corruption bug in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine, the engine that runs Java programs. Crafted Base64 input could crash the JVM and open the door to remote code execution by an attacker who never logs in.

## What the bug is

Base64 turns binary data into plain text, and Java uses it everywhere from login tokens to file uploads. To decode it faster, OpenJDK includes hand-written assembly that uses AVX-512 VBMI instructions on supporting Intel and AMD chips. [AVX-512, Intel’s 512-bit vector instruction set](https://en.wikipedia.org/wiki/AVX-512), lets a processor handle 64 bytes in one step.

The security firm Calif, which found and reported the flaw, explains in [its Java4Shell technical write-up](https://calif.io/java4shell) that this fast path mishandles a stray padding character at the end of the input. For a 65-character string, Java sets aside a 50-byte result array, but the routine computes a negative length and performs a full 64-byte write, spilling 62 bytes past the end of the array. Java rejects the bad input afterward, but by then neighboring data in memory may already be damaged.

Calif researcher Quang Luong said the bug took about an hour to find with an AI coding agent and two more hours to turn into a first working exploit, at a token cost under $200. The firm says it demonstrated pre-login code execution against default setups of Keycloak, Jira, Confluence, JFrog Artifactory, Jenkins and PingFederate, and is withholding those product-specific exploits for now.

## Who must patch

Oracle’s entry in [the National Vulnerability Database record for CVE-2026-114938](https://nvd.nist.gov/vuln/detail/CVE-2026-114938) lists affected Oracle Java SE builds: 8u511b33-perf for Java 8, 17.0.21.0.3 for Java 17, 21.0.13.0.3 for Java 21, 25.0.5.0.3 for Java 25 and 27.0.1.0.3 for Java 27, plus GraalVM for JDK 17 and 21 and GraalVM Enterprise Edition 21.3.20.0.3. Oracle rates it 8.1 out of 10 under CVSS 3.1; Calif scores it 9.2 under the newer CVSS 4.0. Here is a quick way to tell whether a machine is in scope:

- **Java version:** Calif says OpenJDK 17.0.6 and newer are affected, along with builds made from it, including Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu and Red Hat OpenJDK.

- **Processor:** the bad code only runs on x86-64 chips with AVX-512 VBMI, such as Intel Xeon from Ice Lake onward and AMD Zen 4 or newer. ARM64 servers are not affected.

- **Exposure:** CISA asks teams to put internet-facing systems first and to look for Java runtimes hidden inside third-party apps, containers and appliances.

Oracle and OpenJDK released fixes at 1 p.m. Pacific time on November 17, according to Calif. For machines that cannot be updated right away, Calif lists two startup flags: -XX:-UseBASE64Intrinsics turns off the accelerated Base64 code, and -XX:UseAVX=2 disables AVX-512 entirely, though it should only be used on x86-64 hosts. CISA also suggests validating and size-limiting Base64 input at the application edge and watching for unexpected JVM crashes.

The fast decoder fits a pattern Badiyaa readers have seen this week: [our explainer on how Base64 encoding works](https://badiyaa.com/base64-encoding-how-it-works/) covers the format itself, and the [nginx flaw that let attackers run code without logging in](https://badiyaa.com/nginx-http2-remote-code-execution/) landed days earlier.

As of CISA’s November 17 assessment, the agency recorded no known exploitation in the wild. Calif says it will publish its weaponized chains for individual products later, once users have had time to upgrade.

## Sources

- [Critical Java Vulnerability Requires Immediate Patching](https://www.cisa.gov/news-events/alerts/2026/11/17/critical-java-vulnerability-requires-immediate-patching), Cybersecurity and Infrastructure Security Agency, 2026

- [Java4Shell technical write-up](https://calif.io/java4shell), Calif, 2026

- [CVE-2026-114938 Detail](https://nvd.nist.gov/vuln/detail/CVE-2026-114938), NIST National Vulnerability Database, 2026

- [AVX-512](https://en.wikipedia.org/wiki/AVX-512), Wikipedia, 2026

*Image: Carl Lender, CC BY 2.0 via Wikimedia Commons*

*This article was produced with AI assistance and reviewed by our Editorial Desk. [How we work](https://badiyaa.com/editorial-policy/).*
