Java4Shell: Red Hat urges immediate patching for critical OpenJDK remote code execution flaw
Tracked as CVE-2026-114938, the Base64 decoding bug sits inside the Java runtime itself on modern AVX-512 servers.
Red Hat and major Java maintainers are urging system administrators to patch immediately after disclosing a critical OpenJDK vulnerability dubbed Java4Shell. Tracked as CVE-2026-114938 and carrying a critical CVSS v4.0 severity score of 9.2, the memory-corruption bug can allow an unauthenticated remote attacker to crash Java applications or achieve arbitrary remote code execution.
Unlike library-level flaws such as Log4Shell, Java4Shell lives directly inside the Java runtime environment. Because enterprise web servers, payment APIs, and authentication gateways routinely decode untrusted Base64 strings before a user is ever authenticated, the attack surface across modern cloud infrastructure is substantial.
Inside the Base64 intrinsic flaw
The bug sits in OpenJDK's hand-optimized assembly code for java.util.Base64.Decoder. To squeeze extra throughput out of modern server chips, the runtime uses specialized vector instructions when decoding Base64 payloads. Researchers discovered that when a malformed Base64 input contains an unexpected sequence of trailing equals-sign padding characters, a length-calculation error triggers an integer underflow.
That underflow causes the decoder to write roughly 62 to 63 bytes beyond the end of an allocated heap memory array. Depending on surrounding memory layout and application behavior, that out-of-bounds write can either terminate the Java Virtual Machine outright or open the door to memory corruption exploits.
Which servers are actually vulnerable
Not every Java deployment is exposed. Exploitation requires a specific combination of Java version and processor architecture. Affected software includes OpenJDK 17.0.6 and later, spanning Red Hat builds of OpenJDK 17, 21, and 25 across Red Hat Enterprise Linux 8, 9, and 10, along with container base images and RHEL CoreOS environments that bundle those runtimes. Older OpenJDK 8 and OpenJDK 11 branches are generally unaffected unless a vendor backported the optimized decoder.
Hardware matters just as much. The vulnerable code path executes only on x86-64 processors that support the AVX-512 VBMI instruction set, including Intel Xeon Ice Lake or newer chips and AMD EPYC Zen 4 or newer server processors. ARM64 environments such as AWS Graviton and older x86-64 hardware without AVX-512 VBMI are not impacted.
Patching and emergency mitigations
Red Hat has published security advisory RHSB-2026-018 alongside expedited patched builds across its supported distributions. Operations teams should run standard package updates via dnf update on affected Linux hosts and rebuild downstream container images as updated base layers arrive. For legacy production services that cannot be restarted immediately, administrators can consult vendor advisories for JVM command-line flags that disable the affected AVX-512 Base64 intrinsic as a temporary stopgap.