Java4Shell Flaw Puts Unpatched OpenJDK Systems at Risk of Remote Code Execution

· Original article ↗

Summary

Java4Shell (CVE-2026-114938) affects unpatched OpenJDK-based runtimes on x86-64 systems with AVX-512 VBMI; researchers demonstrated pre-authentication RCE in several products. Oracle issued fixes, and Qualys outlines workarounds and remediation priorities.

Key points

  • The flaw is a memory corruption bug in OpenJDK’s AVX-512-optimized Base64 decoder; malformed input can write 62 bytes beyond a buffer.
  • Affected systems require both an unpatched in-scope Java runtime and x86-64 hardware with AVX-512 VBMI, as well as attacker-controlled input reaching the vulnerable decoding path.
  • Researchers demonstrated pre-authentication RCE in default configurations of Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate; other products required authentication.
  • The article says public exploitation had not been confirmed as of November 17, 2026, but the root cause and technique were public.
  • Oracle released fixed builds on November 17, 2026; the article also identifies Amazon Corretto 17.0.21.1.2 as fixed.
  • Until patching, the preferred workaround is the JVM flag -XX:-UseBASE64Intrinsics; -XX:UseAVX=2 is an alternative for Intel and AMD servers. Both require restarting JVMs and do not replace patching.
  • Qualys recommends prioritizing internet-facing identity, build, and collaboration systems, checking bundled runtimes, and monitoring for unexpected JVM crashes, shells, outbound connections, and unaccounted runtimes.

Article Details

Vulnerability Types
  • Memory corruption
  • Out-of-bounds write
Severity
Critical; researchers rated it 9.2 under CVSS v4.0, and Oracle rated it 8.1 under CVSS v3.1.
Affected Versions
  • Unpatched OpenJDK-based builds 17.0.6 and later, including versions 21, 25, and 27, on x86-64 processors with AVX-512 VBMI
  • Oracle Java SE 8 Enterprise Performance Pack 8u511b33-perf
Exploitation Status
not_reported
Exploit Availability
claimed_or_private
Patch Status
available
Workarounds
  • Start the JVM with -XX:-UseBASE64Intrinsics and restart it; this is the preferred temporary workaround.
  • On Intel and AMD servers, start the JVM with -XX:UseAVX=2 and restart it.
  • While awaiting a patch, take identity, build, and collaboration consoles off the public internet or place them behind a VPN.

MITRE ATT&CK

CVE

Vendors

Products

Related Articles