How One Base64 Bug Can Leak Your Java Heap (Java4Shell, CVE-2026-114938)
Most Java4Shell (CVE-2026-114938) coverage on day one was either "your servers are on fire" or "it only crashes the JVM." Both skip the mechanism, and the mechanism tells you who is at risk. This post walks through why the bug exists, what the sources actually established, and what a defender can watch for.
I have not reproduced the bug. Everything below comes from public write-ups by Upwind, Endor Labs, Equixly, Qualys and Calif, and I flag where they disagree.
TL;DR
Claim Status
Heap write past the output array on x86-64 with AVX-512 VBMI Reproduced by Endor Labs (under an emulator) and Upwind (on real hardware)
JVM crash from a remote request Consistent across sources
Pre-auth RCE in named products Claimed by Calif, no public proof-of-concept
Attacker-controlled write contents Not supported, the written bytes are constant
Exploited in the wild None reported, not in CISA KEV as of November 17
Why an intrinsic exists at…