Developing threat · updated Nov 17, 2026

Java4Shell.
Are you exposed?

CVE-2026-114938 · pre-auth · OpenJDK Base64 decoder

A reported pre-authentication flaw in Java's AVX-512 Base64 decoder. Details leaked before Oracle's patch. Here's what we know, who's at risk, and what to do right now.

Analysis by Upwind Research & MDR

30-second exposure check

Tick everything that's true for any of your workloads.
Likely in scope. Apply the stopgap below and contact our team if you see JVM crashes or Java spawning shells.
Lower risk on these answers. Java 8/11 and ARM (e.g. Graviton) are out of scope by our reading. Confirm in the blog.
What we know

The short version

Upwind's reading of the OpenJDK source, ahead of vendor confirmation. Versions and impact may change as Oracle publishes.

!

The bug

Integer underflow in the AVX-512 Base64 padding path leads to a heap overflow inside the JVM.

Pre-authHeap overflow
?

The impact

Reported as RCE. Not proven yet; the most likely outcome today is a JVM crash (remote DoS).

DoS likelyRCE unconfirmed
✓

Who's in scope

Java 17.0.6+, 21, 25, 27 on AVX-512 VBMI x86-64. Java 8/11 and ARM aren't affected by our reading.

17 · 21 · 25 · 278 · 11 · ARM
Do this now

Four steps for security teams

01

Inventory

Find every Java 17/21/25/27 runtime, including those inside containers and vendor products.

02

Prioritize

Internet-facing workloads on AVX-512 capable CPUs first.

03

Stopgap

Test disabling the intrinsic. Slows Base64 decoding.

-XX:-UseBASE64Intrinsics
04

Patch & watch

Patch when Oracle ships. Alert on JVM crashes and Java spawning shells. Beware fake PoCs.

Stopgap flag is not vendor-confirmed. Take version numbers from Oracle's advisory once published.

Upwind customers

Already running Upwind?

See exposed Java runtimes by version and CPU, and get runtime detection for post-exploitation behavior. Full details in the blog.

Taking you to the full analysis in 15s