Reported Java4Shell Flaw in OpenJDK Base64 Decoder Raises Remote Code Execution Risk
Vulnerability Disclosure · 22 sources · Updated 1m ago · First seen Nov 17, 2026

Security researchers report that Java4Shell, tracked as CVE-2026-114938, is a memory-corruption vulnerability in OpenJDK’s hardware-accelerated Base64 decoder that could enable unauthenticated remote code execution. Oligo describes a crafted 65-byte input triggering an integer underflow in padding handling, producing a 62-byte heap buffer overflow that could corrupt adjacent Java objects. Exposure depends on the OpenJDK build, whether the vulnerable AVX-512 decoding path is available and enabled on x86 hardware, and whether attacker-controlled input reaches the decoder. Aikido cites early reports identifying OpenJDK 17 builds from 17.0.6 onward and a CVSS 4.0 score of 9.2, but says Oracle had not confirmed the CVE or technical details as of November 17, 2026.
Neither source provides evidence of exploitation in the wild, and affected-version boundaries and fixed builds remain unconfirmed. Oracle separately announced 11 Java SE patches for remotely exploitable, unauthenticated vulnerabilities across several release lines, but their mapping to individual flaws was unpublished; that announcement does not establish Java4Shell’s scope. Organizations should inventory Java runtimes, including bundled JDKs and container images, identify applications exposing Base64 decoding to untrusted input, and track vendor-specific fixes. Oligo identifies disabling the affected acceleration path or Base64 intrinsics as possible temporary mitigations, subject to vendor guidance and validation; these measures are not substitutes for patching.


