Java4Shell Flaw Can Enable Code Execution on Some AVX-512 Java Servers

· Original article ↗

Summary

Java4Shell (CVE-2026-114938) is a Java Base64 decoder heap overflow affecting certain runtimes on x86-64 CPUs with AVX-512 VBMI. Researchers demonstrated code execution on some apps; no in-the-wild exploitation was reported as of Nov. 18, 2026.

Key points

  • Malformed Base64 ending in an unexpected = can make the JIT-compiled AVX-512 decoder write 62 or 63 bytes beyond its output array.
  • Exposure requires a vulnerable Java build, an x86-64 CPU with AVX-512 VBMI, and an application that passes attacker-controlled input to the decoder.
  • Calif reports pre-authentication code execution on six applications, including Jira, Jenkins, and Keycloak; exploitation is target-specific, and some listed applications require login.
  • Independent labs reproduced crashes and JavaBleed memory reads, but did not reproduce remote code execution. No exploitation in the wild had been reported as of Nov. 18, 2026.
  • Oracle and OpenJDK shipped fixes on Nov. 17; the article lists fixed releases for several Java distributions and says Red Hat fixes were not yet released as of Nov. 18.
  • Recommended mitigations include installing fixed builds, disabling Base64 intrinsics if patching is delayed, validating inputs, and limiting unauthenticated access.

Article Details

Vulnerability Types
  • Heap buffer overflow
  • Out-of-bounds write
Severity
Critical; reported scores vary: Calif 9.2 (CVSS 4.0), Red Hat 9.8 preliminary, Amazon 8.8, and Oracle/OpenJDK 8.1 (CVSS 3.1).
Affected Versions
  • Oracle Java SE 17: 17.0.6 and later, before 17.0.21.1
  • Oracle Java SE 21: before 21.0.13.1
  • Oracle Java SE 25: before 25.0.5.1
  • Oracle Java SE 27: before 27.0.1.1
  • Amazon Corretto 17, 21, 25, and 27: before 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, and 27.0.1.1.4, respectively
  • Azul Zulu 17, 21, 25, and 27: before 17.70.201, 21.54.201, 25.38.201, and 27.30.201, respectively
  • Java SE 8 Performance Pack: 8u511b33-perf
Exploitation Status
not_reported
Exploit Availability
claimed_or_private
Patch Status
partial
Workarounds
  • Start the JVM with -XX:-UseBASE64Intrinsics to disable the vulnerable Base64 path.
  • On x86-64 only, use -XX:UseAVX=2 to disable AVX-512.
  • Validate Base64 input at application boundaries, enforce input-size limits, and limit unauthenticated access.

MITRE ATT&CK

CVE

Vendors

Products

Related Articles