Java4Shell checker
Find out whether your Java runtime is exposed to the Java4Shell OpenJDK Base64 heap overflow. A local version + CPU check — no payloads, no probing, no data leaves your browser.
Am I vulnerable?
Check your own Java version and CPU against CVE-2026-114938. Runs entirely in your browser — nothing is sent anywhere, and no server is probed.
Why there's no "enter a URL" scan: the only reliable trigger for this bug crashes the target JVM, so there is no safe remote probe. The honest signal is your host's own JDK build and CPU — which is what this checks.
The bug lives in an x86 AVX-512 VBMI intrinsic (Intel Ice Lake+, AMD Zen 4+). ARM64 and older x86 never run it — immune regardless of Java version.
On an affected CPU, Java 17.0.6–17.0.21, and every 21 / 25 / 27 before the fixed build, take the vulnerable Base64 path. 11 and earlier don't ship the intrinsic.
Fixed in 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 (Oracle Nov 2026 CPU). At or above your train's fixed build = not affected.
Frequently asked questions
What is Java4Shell (CVE-2026-114938)?
Java4Shell is a heap buffer overflow in OpenJDK’s AVX-512 Base64 decoding intrinsic. A short malformed Base64 input makes the hand-written assembly write 62 bytes past the end of a heap buffer before Java rejects the input (CWE-191 leading to CWE-122). It affects OpenJDK-based Java on x86 CPUs with AVX-512 VBMI and carries a CVSS 9.2 (4.0) rating.
Does this tool scan a remote URL for Java4Shell?
No. Unlike an HTTP-level flaw, the only reliable way to trigger this bug is to feed malformed Base64 into the Java Base64 decoder, which crashes the whole JVM process. There is no safe, non-destructive remote probe, so a public "enter a URL" scanner would mean attacking a stranger’s server. This checker instead evaluates the JDK version and CPU you already know about your own host — entirely in your browser.
Which Java versions are affected?
On an x86 CPU with AVX-512 VBMI, Java 17.0.6 through 17.0.21, and every Java 21, 25 and 27 release before the fixed build, are affected. Java 11 and earlier do not ship the AVX-512 Base64 intrinsic. Fixes shipped in 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 (Oracle’s November 2026 Critical Patch Update).
Which CPUs are affected?
Only x86-64 CPUs with AVX-512 VBMI — Intel Ice Lake / Sunny Cove and newer, and AMD Zen 4 and newer. ARM64 (AWS Graviton, Ampere, Apple silicon) and older x86 CPUs never execute the vulnerable intrinsic, so they are not affected regardless of Java version.
Is Java4Shell being actively exploited as RCE?
The discloser (Calif) claims pre-authentication remote code execution against products that decode attacker-controlled Base64 before auth (Keycloak, Jenkins, Jira, Confluence, Artifactory, PingFederate). At time of writing, independent vendors had not publicly reproduced full RCE beyond a JVM crash, and the CVE record was still being published. Treat it as a confirmed memory-safety bug with disputed remote-RCE impact — and patch regardless.
How do I fix or mitigate Java4Shell?
Upgrade to the patched build for your train (17.0.21.1 / 21.0.13.1 / 25.0.5.1 / 27.0.1.1 or later). If you cannot patch immediately, start the JVM with -XX:-UseBASE64Intrinsics to disable the vulnerable intrinsic, or -XX:UseAVX=2 to cap AVX usage on x86. Test the flag in staging first — neither Oracle nor OpenJDK has formally confirmed the workaround.
This checks one runtime. O3 checks your whole fleet.
Inventory every JVM, container image, and build dependency, match them against Java4Shell and every other critical CVE, and prioritize by what's actually reachable — from code to runtime.