Java4Shell
OpenJDK Base64 overflow
A heap buffer overflow in OpenJDK's AVX-512 Base64 decoder. A short malformed input writes 62 bytes past a heap buffer inside the JVM itself — reachable by any Java service that decodes attacker-controlled Base64. Below is the global exposure of the products named as pre-auth reachable.
A bug in the JVM, not your code
Java4Shell (CVE-2026-114938) is an integer underflow in the hand-written x86 assembly for AVX-512 Base64 decoding. A 65-byte malformed input makes the VMOVDQU8 write run 62 bytes past the end of a heap buffer before Java throws — corrupting adjacent JVM memory (CWE-191 → CWE-122).
It triggers anywhere untrusted Base64 reaches java.util.Base64 — which is why products that decode auth headers or tokens before login are named as pre-auth reachable. Two gates must both be true: an affected JDK build and an x86 CPU with AVX-512 VBMI.
Two conditions to be affected
-XX:-UseBASE64Intrinsics or -XX:UseAVX=2Exposure by affected product
Internet-facing instances of the products the Java4Shell PoC names as pre-auth reachable. This is attack surface, not confirmed-vulnerable: an instance is only at risk on an affected JDK + AVX-512 CPU.
Exposure breakdown
Where affected-product instances concentrate, and how this threat scores across the standard risk signals. Note the disputed exploitation status.
Top countries by affected products
Internet-facing instances of named pre-auth products
Exposure by region
Share of affected-product instances worldwide
Threat scoring
As of 2026-11-18
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H (as claimed)Counts are internet-facing instances of products the Java4Shell PoC names as pre-auth reachable. This is an ATTACK-SURFACE proxy, not a vulnerability census: an instance is affected only if it runs an unpatched JDK (17.0.6–17.0.21 / <21.0.13.1 / <25.0.5.1 / <27.0.1.1) on an x86 CPU with AVX-512 VBMI. Remote exploitation beyond a JVM crash has not been independently reproduced at time of writing.
Is your Java runtime affected?
Check your JDK version and CPU against Java4Shell in seconds — a local check, no probing, nothing leaves your browser.
Open the Java4Shell checker