Posted in Threat Intelligence

Java4Shell is public now — here's who it actually hits. CVE-2026-114938 is a heap out-of-bounds write in…

Schomer — Founder & Security Architect | Pre-Parser Enforcement, Offensive Research & Deterministic Security Tooling

Java4Shell is public now — here's who it actually hits.

CVE-2026-114938 is a heap out-of-bounds write in HotSpot's hand-written AVX-512 Base64 decoder. The trigger is 65 characters, and it only fires when the CPU has all four flags: avx512f, avx512bw, avx512vbmi, bmi2. Intel Ice Lake / Sapphire Rapids or newer, AMD Zen 4 or newer. ARM64 is not affected at all.

Affected: OpenJDK 17.0.6–17.0.21, 21, 25, 27. Fixed builds are out since Nov 17 (17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1). Calif demoed unauthenticated RCE against default Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate. No confirmed exploitation in the wild as of Nov 18, but PoC code is circulating.

What to do: check your Java version and your CPU flags first. If you don't have all four flags, this CVE doesn't apply to that host even on an affected JDK. If you do, patch — or as a stopgap, -XX:-UseBASE64Intrinsics or -XX:UseAVX=2.

One honest note: a pre-parser gate doesn't block this. The corruption happens inside the JVM, after the bytes are already in the process. The fix is the patched JDK, not a filter in front of it.

Same week, nginx has its own pair — CVE-2026-123007 and CVE-2026-123633, both 9.2, both need HTTP/2 on. Fixed in 1.30.7 stable / 1.31.9 mainline. Check your version and whether http2 is actually enabled in your config.

2 reactions · 0 comments

Read and join the discussion on Cyberr