Cybersecurity Research

Java4Shell: A Flaw Inside the Java Runtime Itself Puts Base64 Handling in the Spotlight

CrowdStrike · 19 Nov 2026
Key Takeaway Find out which of your Java applications run on modern AVX-512 hardware and accept Base64 input from the internet, and patch those first.

CVE-2026-114938, nicknamed "Java4Shell", is a memory corruption vulnerability in HotSpot, the Java Virtual Machine shared by Oracle Java SE, OpenJDK and many downstream distributions. Oracle and OpenJDK released fixes on November 17, 2026. Oracle rates the flaw 8.1 (High), while Red Hat rates it 9.8 (Critical).

The problem sits in an optimised Base64 decoding routine that the JVM uses only on processors supporting AVX-512 VBMI, which includes Intel Ice Lake and newer, and AMD Zen 4 and newer. An unauthenticated remote attacker who can pass a crafted Base64 string to an affected application can trigger an out-of-bounds heap write of up to 62 bytes. Base64 is common in credentials in HTTP Basic authentication headers, JSON Web Tokens, SAML assertions and file uploads, so the vulnerable code is often reachable before any application checks run.

What sets this flaw apart is where it lives. The defect is in the runtime, not in an application or library, so an application that decodes attacker-supplied Base64 with the standard Java class library is exposed even if its own code is sound. That reaches OpenJDK builds from multiple vendors, bundled runtimes, container images and managed cloud services.

Exposure is narrower than the footprint suggests. Exploitation needs an affected Java version, supported hardware and an application decoding attacker-supplied Base64. ARM64 and i386 systems are not affected, and standard Java 8 and 11 are not affected (the Oracle Java 8 Performance Pack is the exception). The small size of the overwrite makes reliable remote code execution difficult, though not impossible. CrowdStrike advises patching systems meeting all three conditions immediately, starting with internet-facing services, and handling the rest through normal patching.

Why it matters

This breaks the assumption that a clean application is a safe one: the flaw is in the runtime, so code review and framework updates will not find it. Teams running Java in containers, bundled runtimes or managed services may not know which JVM version or hardware they are on, which makes the three-condition test hard to apply without a proper inventory. Internet-facing services that decode authentication headers or tokens are the clearest priority.

What to do

  • Patch affected Java 17, 21, 25 and 27 runtimes to 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1, starting with internet-facing services.
  • Check for the Oracle Java 8 Performance Pack (8u511b33-perf), the only Java 8 build affected.
  • Inventory Java runtimes bundled inside applications and container images, not just system-wide installs.
  • Watch for web shell deployment and suspicious child processes spawned by Java processes.
Java CVE-2026-114938 Vulnerability Patch Management JVM

Summarised by CISO AI from CrowdStrike, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.