NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Threat Center›Java4Shell
CVE-2026-114938 · CVSS 9.2

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.

108,582
affected-product instances exposed
47
countries with exposure
Global exposure
Shodan · 2026-11-18
High exposureModerateLow
Hover or tap a location. 105,363 affected-product instancesacross 47 countries.
108,582
Affected-product instances
internet-facing
5
Pre-auth products
named in the PoC
47
Countries exposed
with named products
United States
Top exposure
28,258 instances

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.

Check your Java version & CPU

Two conditions to be affected

x86 CPU with AVX-512 VBMI
Intel Ice Lake+ or AMD Zen 4+. ARM64 (Graviton, Ampere, Apple) and older x86 never run the vulnerable intrinsic.
Unpatched OpenJDK build
Java 17.0.6–17.0.21, or any 21 / 25 / 27 before the fix. Java 11 and earlier don't ship the intrinsic.
Fixed in (Oracle Nov 2026 CPU)
17.0.21.1 · 21.0.13.1 · 25.0.5.1 · 27.0.1.1
Interim: -XX:-UseBASE64Intrinsics or -XX:UseAVX=2

Exposure 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.

Keycloak
29,859
Jenkins
40,226
Jira
7,360
Confluence
30,244
Artifactory
893

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

Asia
36.2k34%
Americas
34.3k33%
Europe
30.8k29%
Oceania
3.0k3%
Africa
1.1k1%

Threat scoring

As of 2026-11-18

CVSS v4.0
9.2
Critical
EPSS
Not scored
too new for EPSS
CISA KEV
Not listed
not in catalog
In the wild
Disputed
probing reported
CVSS vector
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