CVE-2026-114938, dubbed "Java4Shell," is a memory corruption vulnerability in the HotSpot Java Virtual Machine (JVM), the runtime shared by Oracle Java SE, OpenJDK, and many downstream Java distributions.
Although HotSpot is widely deployed, exposure to this vulnerability is narrower than its footprint suggests. Exploitation requires three conditions: an affected Java version, x86-64 hardware that supports AVX-512 VBMI, and an application that decodes attacker-supplied Base64 data. Even when all three are met, the limited size of the memory overwrite makes reliable remote code execution difficult, though not impossible.
Oracle and OpenJDK released fixes on November 17, 2026. Organizations should patch systems that meet all three conditions immediately, starting with internet-facing Java services. Remaining Java deployments can be addressed through regular scheduled patching.
Oracle rates the vulnerability 8.1 (High) under CVSS 3.1. Red Hat rates it 9.8 (Critical) under CVSS 3.0. Oracle and OpenJDK released fixes on November 17, 2026.
What Is Java4Shell?
The flaw resides in HotSpot's AVX-512-optimized Base64 decoding routine, a performance shortcut the JVM uses only on processors that support AVX-512 Vector Byte Manipulation Instructions (VBMI). Base64 is everywhere in modern applications. It carries credentials in HTTP Basic authentication headers, encodes JSON Web Tokens (JWTs) and SAML assertions, and wraps file uploads and binary API payloads. As a result, the vulnerable code path is frequently reachable from untrusted input before any application-level validation takes place.
What elevates this vulnerability is its placement in the stack. The defect sits in the runtime itself, rather than an application, framework, or library. An application that decodes attacker-supplied Base64 using the standard Java class library is exposed even if its own code is flawless. Because the vulnerable code lives in shared HotSpot code, exposure extends beyond Oracle-branded Java. It includes OpenJDK builds from multiple vendors, applications that bundle their own Java runtime, container images, and managed cloud services.
Java4Shell also has meaningful constraints. The vulnerable code path is only active on specific x86-64 hardware, and the size of the out-of-bounds write is limited.
An unauthenticated remote attacker who can pass a specially crafted Base64 string to an affected application can trigger an out-of-bounds heap write of up to 62 bytes. Because the overflow lands on the Java heap, its consequences depend on what sits adjacent to the destination buffer when the write occurs. These may include:
- Denial of service: Corrupting object headers or JVM metadata causes the JVM to crash. This would be the most likely outcome.
- Memory disclosure ("JavaBleed"): Under certain conditions, corruption of adjacent object state can cause the application to return heap contents it should not. This could include fragments of other requests, session tokens, or credentials.
- Remote code execution: Achieving code execution requires the attacker to influence heap layout precisely enough that the limited overwrite corrupts a security-relevant structure, such as an object header, array length, or reference, in a way that can be leveraged further. The 62-byte ceiling, hardware dependency, and variability of heap layout across JVM versions, garbage collectors, and workloads make this the most difficult outcome to reliably achieve.
Several conditions must be met at once for successful exploitation to occur.
- First, the Java runtime must match with the affected software.
- Second, the runtime must be running on an x86-64 processor that supports AVX-512 VBMI, such as Intel Ice Lake or newer or AMD Zen 4 or newer. On supported hardware, HotSpot enables the vulnerable AVX-512 Base64 decoding routine by default, so no special configuration is needed for a JVM to be exposed.
- Finally, an attacker must be able to deliver a specially crafted Base64 string to an application that decodes it using the standard Java class library. Common entry points include authentication headers, tokens, and file uploads, which are often processed before authentication completes. Denial of service is the most reliable outcome. Remote code execution additionally requires the attacker to shape heap memory precisely enough for the limited 62-byte overwrite to corrupt a useful structure, which significantly constrains large-scale exploitation.
Who Is Affected?
Exposure depends on both hardware and software.
Affected Hardware
Only x86-64 processors that support AVX-512 VBMI are affected. This includes Intel Ice Lake and newer, and AMD Zen 4 and newer. ARM64 and i386 systems are not affected.
Affected Software
| Branch | Affected Versions | Fixed Version |
| Java 17 | 17.0.6 through 17.0.21 | 17.0.21.1 |
| Java 21 | Up to 21.0.13 | 21.0.13.1 |
| Java 25 | Up to 25.0.5 | 25.0.5.1 |
| Java 27 | Up to 27.0.1 | 27.0.1.1 |
| Oracle Java 8 Performance Pack | 8u511b33-perf | See Oracle advisory |
Standard Java 8 and Java 11 environments are not affected. The Oracle Java 8 Performance Pack is the exception.
Downstream distributions are also affected. These include, but are not limited to:
- Amazon Corretto
- Eclipse Temurin
- Microsoft Build of OpenJDK
- Azul Zulu
- Red Hat OpenJDK
- Oracle GraalVM
- BellSoft Liberica
- SAP SapMachine
What Should Organizations Do Now?
- Upgrade to patched versions. Apply the fixes from Oracle's and OpenJDK's Critical Security Patch Update for November 2026, or the equivalent update from your Java vendor.
- Restart running JVMs. Upgrading the runtime on disk does not protect processes that are already running. Restart all Java processes after patching.
- Rebuild container images. Rebuild images on patched base images and redeploy them.
- Inventory embedded runtimes. Many appliances and third-party applications ship their own Java runtime. Check vendor advisories and review the CISA alert on CVE-2026-114938.
How the CrowdStrike Falcon Platform Helps
CrowdStrike employs a layered approach to detecting adversary activity, using machine learning and behavior-based detections, including indicators of attack (IOAs). The CrowdStrike Falcon platform provides out-of-the-box visibility and detection coverage for post-exploitation activity that may follow exploitation of CVE-2026-114938. Existing IOAs detect and prevent common post-exploitation activity, including web shell deployment, suspicious child processes spawned by Java processes, hands-on-keyboard activity, and living-off-the-land techniques.
The Falcon platform also identifies the attack surface and exposure to the vulnerability using CrowdStrike Falcon® Exposure Management and CrowdStrike Falcon® Cloud Security’s Image Assessment functionality.
Falcon Exposure Management Finds Vulnerable Java Runtimes
Falcon Exposure Management provides comprehensive visibility across affected environments. Sensor-based assessment identifies Java runtimes affected by CVE-2026-114938 on supported Windows, Linux, and macOS hosts. This covers Oracle Java SE, OpenJDK, and downstream distributions such as Amazon Corretto, Eclipse Temurin, Microsoft Build of OpenJDK, Azul Zulu, Red Hat OpenJDK, Oracle GraalVM, BellSoft Liberica, and SAP SapMachine.
Falcon Exposure Management flags hosts running affected versions: Java 17 (17.0.6 through 17.0.21), Java 21 (up to 21.0.13), Java 25 (up to 25.0.5), Java 27 (up to 27.0.1), and the Oracle Java 8 Performance Pack (8u511b33-perf). Hosts updated to 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1 are no longer flagged.
Falcon Exposure Management detects standard Java installations on all supported sensor versions. These checks have no minimum sensor version requirement:
- Windows: standard Windows installs
- Linux: rpm and dpkg package installs
- macOS: dmg installs
CrowdStrike has also added the following sensor-based detections. They find Java installations that the standard checks might miss, such as custom installs or runtimes bundled with other applications. They are available only on the sensor versions listed:
Windows (Falcon sensor 7.40 or later): A system-wide check for Java installations. This requires “Enable Full System Visibility” to be turned on in the Exposure Management policy (checks on C: drive only; if C: is not the default drive the in-depth check does not work).
Linux (Falcon sensor 7.31 or later): A check of running processes to identify Java installations performed outside the package manager.
Customers on earlier sensor versions are still covered by the standard install checks. They will not get the additional system-wide and running-process checks until they upgrade.
CrowdStrike has updated Falcon Exposure Management detections on all supported platforms to flag only x86-64 systems, and is adding a check on Linux for whether AVX-512 VBMI support is enabled. This hardware check (AVX-512 VBMI support) is available on Linux only. On Windows and macOS, Falcon Exposure Management may flag hosts that are not exploitable, so customers should prioritize patching on systems with supported processors.
Falcon Exposure Management and Falcon Spotlight customers can find exposed hosts in the Falcon console under Exposure Management > Vulnerability Management > Vulnerabilities.