Note: This post was written by Claude Opus 5.5. The following is a synthesis of advisories from OpenJDK, CISA and Red Hat, write-ups from the researchers who found and tested the flaw, and reporting from SecurityWeek.
A flaw in the code Java uses to decode Base64, the text format that carries login tokens, file uploads and other data between systems, can let an attacker crash a Java application and, with enough work, take it over. CVE-2026-114938, which the researchers who demonstrated it named Java4Shell, affects Java 17, 21, 25 and 27 on servers with newer Intel and AMD processors. Oracle and the OpenJDK project shipped fixes on November 17, and CISA “strongly urges organizations to immediately patch.” A patched runtime protects nothing, though, until every program using it restarts, and many of those applications are vendor products carrying their own copy of Java.
What CVE-2026-114938 does
The bug sits in a shortcut that HotSpot, Java’s runtime engine, takes to decode Base64 on x86-64 processors that support a set of instructions called AVX-512 VBMI. Malformed input ending in a stray padding character makes that code write about 62 bytes past the end of its buffer, corrupting whatever sits next to it in memory. Calif, the security firm that disclosed it, says the trigger is 64 letters followed by an equals sign.
What an attacker can do with that varies. VulnCheck, which reproduced the bug, found that crashing an affected server is trivial with a burst of requests to any feature that decodes attacker-supplied Base64. Calif reports reading server memory, as Heartbleed did, and running code without logging in on default installations of Jira, Confluence, Jenkins, Keycloak, JFrog Artifactory and PingFederate, though each product needed its own exploit chain. It also says a Java program that merely connects to a malicious server can be compromised.
Red Hat rates the flaw Critical, saying it “allows unauthenticated remote code execution” and can expose memory holding “credentials, private keys, and session tokens.” Oracle, which assigned the CVE, scores it 8.1 out of 10 and calls it difficult to exploit.
Which Java versions and servers are exposed
The flaw affects OpenJDK 17.0.6 and later, plus versions 21, 25 and 27, and the distributions built from them, including Amazon Corretto, Eclipse Temurin, Microsoft’s build, Azul Zulu and Oracle Java SE. OpenJDK’s advisory doesn’t mark Java 8 or 11, though Oracle lists the Performance Pack build of Java 8 as affected.
The processor matters as much as the version. The vulnerable code runs only on chips with AVX-512 VBMI: Intel Xeon processors from Ice Lake onward, and AMD’s Zen 4 and newer, including EPYC servers and Ryzen 7000 and 9000 desktops. VulnCheck notes that most Intel desktops and laptops since 2021’s Alder Lake lack the feature, and ARM processors such as Amazon’s Graviton aren’t affected.
On Linux, Calif’s check lists the four processor flags the bug needs. A vulnerable host prints all four:
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
Censys advises using the result to decide what to patch first, not to rule a server out, since a virtual machine can land on a different processor after a resize or migration.
Fixes shipped November 17, but restarts finish the job
Oracle’s patched builds are numbered 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, and distributions add their own suffixes; Amazon’s Corretto 17 update, for example, is 17.0.21.1.2. Microsoft, Azul and Red Hat have also shipped updates.
Installing the update is half the work. A running Java process keeps the old code loaded until it starts again, which is why the Jenkins project tells users to update Java and then restart Jenkins. CISA’s first step is finding Java at all, including runtimes “bundled with third-party applications or included in container images and appliances,” which “may not appear as separate entries in software inventories.”
Those bundled copies wait on their vendors. Cisco says more than a dozen of its products are affected, among them Catalyst Center and Secure Network Analytics, with no fixes or workarounds yet, SecurityWeek reported. Atlassian advises Data Center customers to disable AVX-512 until patches arrive, and Keycloak replaced container images that shipped a vulnerable Java build. Where updating isn’t possible yet, Calif lists two Java startup options that switch off the vulnerable code path, and VulnCheck found that both stopped the overflow in its tests. Censys advises trying either one on a test system first, because a Java runtime that rejects an unfamiliar option refuses to launch.
Probing so far, not confirmed exploitation
Attackers have started looking. By early November 19, GreyNoise had recorded more than 150 requests shaped like a Java4Shell attack from five IP addresses, with no successful intrusions on its sensors, SecurityWeek reported, and Cisco said it knew of no malicious use. The flaw was not on CISA’s Known Exploited Vulnerabilities list as of the catalog’s November 20 update. Attack code is spreading anyway: public repositories claim working chains that no one has verified, and VulnCheck offers a full exploit to subscribers of its threat intelligence.
The bug was public in June
Java4Shell wasn’t new when Calif found it. According to Calif’s timeline, a Java user hit the crash and reported it to the Adoptium project on June 9. In September, a developer identified the root cause and proposed a fix to OpenJDK, but the change was closed without being merged.
Calif’s Quang Luong rediscovered the bug on October 24 by asking OpenAI’s Codex to audit the Java runtime for reachable flaws. Calif says Codex found it within an hour, a first working exploit took two more hours, and the AI costs came to less than $200. Oracle shipped the fix 24 days later, after Calif demonstrated attacks on Elasticsearch, Jenkins and Keycloak. Calif saw the same sequence with PHP2Shell in October: “The bug had already been reported, but it was patched only after we showed it could be exploited.”
What to watch
- Vendor patches. In the latest reports, Cisco, Elastic and Atlassian’s Data Center products were still waiting on fixes.
- CISA’s catalog. A listing would mean confirmed attacks, and a remediation deadline for federal agencies.
- Calif’s exploit chains. The firm says its per-product attacks “stay private until everyone has had a chance to upgrade. We will publish them later.”
Until then, the fix has two steps, not one: update Java, then restart everything that runs it.
Sources
- OpenJDK - Vulnerability Advisory: 2026/11/17
- CISA - Critical Java Vulnerability Requires Immediate Patching
- CVE.org - CVE-2026-114938
- Red Hat - CVE-2026-114938
- Calif - Java4Shell: Write once, RCE everywhere
- VulnCheck - Java4Shell CVE-2026-114938: Fine, I Guess We’ll Do This Again
- Censys - OpenJDK Remote Code Execution (Java4Shell) advisory
- Amazon Corretto 17 - Changelog
- ThreatDefence - Java4Shell CVE-2026-114938: Java 17 to 27 Fixes and Hunting
- SecurityWeek - Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories
- CISA - Known Exploited Vulnerabilities Catalog
