Detection Coverage - Java4Shell (CVE-2026-114938)

Observations

Java4Shell (CVE-2026-114938) is a vulnerability in OpenJDK’s AVX-512 Base64 decoder. Public research has shown that malformed base64 values containing non-RFC-compliant tail fragments can trigger an integer underflow during AVX-512 tail processing, resulting in an out-of-bounds write before the input is rejected. Because the vulnerable condition occurs during decoding, the bug can be reached regardless of the application feature, protocol, or input source that ultimately passes the malformed data to java.util.Base64.Decoder.

From a NIDS rule-writing perspective, Java4Shell attempts do not expose consistent network artifacts that can be reliably anchored to or matched on, making it difficult to develop high-fidelity signatures. As a result, our hunting rules focus on the non-RFC-compliant Base64 structure itself rather than specific proof-of-concept strings or application artifacts, since those approaches are more likely to introduce false-negative coverage gaps.

In addition to the generalized hunting coverage, we also included two rules derived from publicly released PoC payloads that look for 64- and 128-character runs of A ending in a single padding character (=) bounded by common delimiter characters, resulting in the same non-RFC-compliant structure. These specific Java4Shell testing patterns are actively being used to identify systems that would process malformed base64 structures.

Per RFC 4648, padding is only valid in the final quartet of a base64-encoded value and may appear only as XX== or XXX=. The malformed endings identified in public research (=, X=, and XX=) don’t meet those requirements and represent the unusual tail-decoding conditions associated with the vulnerable AVX-512 code path.

Conceptually, the signatures look for:

(base64 quartets){16,} + (= | X= | XX=)

We encourage testing and tuning to your own environments before enabling them in production. The intent of these rules is to provide visibility into traffic patterns associated with publicly documented Java4Shell trigger conditions while additional research on exploitation and detection continues to emerge.

Rules

These signatures have been released disabled by default.

  • ET HUNTING Java4Shell Non-RFC Base64 Trailing Fragment in HTTP URI (CVE-2026-114938) (SID: 2072832)
  • ET HUNTING Java4Shell Non-RFC Base64 Trailing Fragment in HTTP Header (CVE-2026-114938) (SID: 2072833)
  • ET HUNTING Java4Shell Non-RFC Base64 Trailing Fragment in HTTP Request Body (CVE-2026-114938) (SID: 2072834)

Generic PoC-Based Signatures

  • ET HUNTING OpenJDK Java4Shell PoC Payload (CVE-2026-114938) M1 (SID: 2072830)
  • ET HUNTING OpenJDK Java4Shell PoC Payload (CVE-2026-114938) M2 (SID: 2072831)
  • ET HUNTING Java4Shell POC User-Agent Observed (CVE-2026-114938) (SID: 2072829)

References

  1. Java4Shell: Write once, RCE everywhere
  2. Java4Shell: Remote Code Execution in OpenJDK (CVE-2026-114938) | Datadog Security Labs
  3. https://www.sentinelone.com/blog/java4shell-vulnerability-in-openjdk-enables-rce-on-avx-512-cpus/
  4. Java4Shell: How a malformed Base64 string breaks the JVM on AVX-512
  5. Java4Shell: From AVX-512 Integer Underflow to Pre-Auth Heap Corruption in Keycloak, Jenkins, and Elasticsearch
1 Like