Menu

Java4Shell (CVE-2026-114938): is your Java server affected?
📰

Java4Shell (CVE-2026-114938): is your Java server affected?

DEV Community: java·Nikoloz Turazashvili (@axrisi)·about 9 hours ago
#tmROpW9g
#devtojava#devto#dev#calif#java
Reading 0:00
15s threshold

Java4Shell is the nickname for CVE-2026-114938, a memory-corruption bug in the Base64 decoder that OpenJDK uses on x86-64 machines with AVX-512 VBMI. The security group Calif says a 65-character string, 64 letter A's followed by an equals sign, makes the decoder write 62 bytes past the end of a 50-byte array. OpenJDK and Oracle published fixes on November 17. If you run Java 17 or newer, the question is whether any of your servers can reach the broken code path, and that takes about four checks.

TL;DR

Calif reports that OpenJDK's AVX-512 Base64 decoder writes 64 bytes into a 50-byte array for a 65-character padded input, so 62 bytes land past the end. Java rejects the input afterwards, which is too late.

Scope: OpenJDK 17.0.6 and newer on x86-64 CPUs with AVX-512 VBMI (Intel Ice Lake or later, AMD Zen 4 or later). ARM64 is not affected. Standard Java 8 and 11 are not on this CVE.

OpenJDK and Oracle list it at CVSS 3.1 8.1; Calif scores it 9.2 on CVSS 4.0.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.