High

CA-26-050: Public PoC Available for CVE-2026-114938 (Java4Shell)

By Adversary Tactics and Intelligence Team

Estimated Reading Time: 7 minutes

Java4Shell | Oracle Java SE | OpenJDK | GraalVM | Public PoC | Remote Code Execution | Heap Buffer Overflow

Source Material: Calif Research,  Cisco Talos,  Oracle November 2026 CSPU,  CISA Alert,  Canadian Cyber Centre Alert  | Technology: Oracle Java SE, OpenJDK and GraalVM | Targeting: Internet-facing and enterprise Java workloads

Executive Summary

CVE-2026-114938, commonly called Java4Shell, is a memory-corruption vulnerability in the hardware-accelerated Base64 decoder used by affected OpenJDK-derived runtimes. Public proof-of-concept code is now available that reliably reproduces the heap out-of-bounds write on compatible systems. 

Exploitation requires an affected Java build on x86-64 hardware with AVX-512 VBMI and related CPU features, the vulnerable intrinsic enabled, and attacker-controlled Base64 data reaching java.util.Base64. Common exposure paths include authentication headers, tokens, SAML messages, cookies, API data, file uploads and some client-side TLS workflows. ARM64 systems are not affected by this hardware-specific code path.

Successful exploitation could crash the JVM, leak sensitive process memory such as tokens and private keys (a technique researchers call JavaBleed), or execute arbitrary code under the Java service account’s privileges. Oracle scores the flaw CVSS 3.1 8.1 (High) and several Linux vendors rate it between 8.8 and 9.8. At the time of publication no in the wild exploitation has been confirmed.

Organizations should patch immediately, prioritizing internet-facing Java services and products with bundled runtimes. Restart all JVMs after updating. Where patching cannot be completed immediately, disable the Base64 intrinsic or AVX-512 as a temporary mitigation.

Threat Overview and Strategic Impact

CVE-2026-114938 stems from an integer underflow (CWE-191) in OpenJDK HotSpot’s AVX-512 Base64 decoding intrinsic that triggers a 62- to 63-byte heap-based buffer overflow (CWE-122). When a short, padded Base64 string is processed after the HotSpot C2 just-in-time (JIT) compiler warms up and selects the vectorized AVX-512 stub, the tail-length calculation goes negative and writes beyond the destination array on the Java heap. Although the decoder subsequently throws a standard IllegalArgumentException, adjacent heap objects are already corrupted.

Within OpenJDK, the vulnerable intrinsic was introduced in version 17.0.6 and affects unpatched 17.x, 21.x, 25.x, and 27.x release lines. Affected Oracle builds prior to the November 17 patch include Java SE 8u511b33-perf (Enterprise Performance Pack); Java SE 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, and 27.0.1.0.3; GraalVM for JDK 17.0.21.0.3 and 21.0.13.0.3; and GraalVM Enterprise Edition 21.3.20.0.3. Standard Java 8 and Java 11 builds do not contain the vulnerable code path. Downstream OpenJDK distributions, including Amazon Corretto, Eclipse Temurin, Azul Zulu, Red Hat OpenJDK, and Microsoft Build of OpenJDK, and third-party appliances or containers that bundle a JRE are also impacted according to each vendor’s patch schedule.

With a deterministic memory-corruption reproducer now public, organizations face an elevated risk of opportunistic scanning and denial-of-service probing. Researchers demonstrated pre-authentication remote code execution against default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate, as well as post-authentication remote code execution against Elasticsearch, Apache Solr, Gerrit, and Spinnaker. Reliable code execution requires tailoring heap layout manipulation to each target application, so no single universal RCE payload exists, though attackers can repeatedly probe services and recover from failed attempts that crash the JVM.

Exposure is highest on internet-facing Java workloads running on Intel Xeon (Ice Lake and newer) or AMD EPYC (Zen 4 and newer) processors where untrusted Base64 inputs reach java.util.Base64. Outbound client-side TLS workflows can also expose internal Java applications if they connect to a malicious server that returns crafted Base64 certificate or handshake data. Because many commercial products and container images ship embedded JREs, updating the host operating system’s default java package alone will not remediate bundled runtimes.

Security Hardening and Recommendations

Inventory all standalone and bundled JVMs across hosts, containers, and third-party appliances, recording both the vendor and exact build string. On Linux hosts, verify CPU exposure by running grep -o avx512vbmi /proc/cpuinfo | head -1; systems that return no output, along with all ARM64 systems, do not execute the vulnerable code path. Prioritize internet-facing services that decode untrusted Base64 prior to authentication.

Deploy patched builds from Oracle or your OpenJDK distribution vendor. Fixed Oracle releases include Java SE 8u513 (for the affected Java 8 Enterprise Performance Pack build), 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1, alongside GraalVM for JDK 17.0.21.1 and 21.0.13.1 and GraalVM Enterprise Edition 21.3.20.1. Rebuild and redeploy container images from patched base layers and restart all running JVMs. Verify the live process runtime directly using jcmd <PID> VM.version (or inspect /proc/<PID>/exe on Linux) instead of checking java -version in the default shell path.

Where vendor patches are pending or cannot be deployed immediately, apply one of the following temporary JVM mitigations and restart the service:

  • Preferred (narrow scope): -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics (disables hardware-accelerated Base64 encoding and decoding without affecting other AVX-512 workloads).
  • Broad x86-64 fallback: -XX:UseAVX=2 (disables all AVX-512 optimizations in the JVM. Apply this flag strictly to x86-64 deployments; ARM64 JVMs do not recognize UseAVX and will fail to start).

For packaged applications or containers where startup command lines cannot be edited directly, pass -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics via the JAVA_TOOL_OPTIONS environment variable and confirm the active flags on the running process. Enforce least privilege on Java service accounts, restrict unnecessary outbound egress, and preserve application, reverse-proxy/WAF, EDR, and JVM crash logs.

Detection Strategy

Correlate edge-request telemetry with host and runtime crash signals, as payload signatures by themselves can miss varied Base64 inputs. Pair spikes in malformed Base64 requests or HTTP 401/403 authentication errors with java.util.Base64 IllegalArgumentException stack traces, HTTP 5xx bursts, JVM hs_err_pid fatal error logs, SIGSEGV crashes, or unexpected container restarts. Because an unaligned heap overwrite frequently crashes the JVM, preserving hs_err_pid artifacts alongside WAF or reverse-proxy logs is critical for separating exploitation probes from routine application errors.

Investigate Java processes that spawn cmd.exe, powershell.exe, /bin/sh, bash, curl, wget, or other unexpected utilities; write executable files; access credential stores; or initiate anomalous outbound connections. Baseline normal Java child-process and egress behavior to reduce false positives.

How Deepwatch Protects Our Customers

Deepwatch helps customers identify the telemetry and asset context needed to prioritize remediation of exposed Java services, including runtime version, internet exposure, CPU capability, and application role. Within available customer telemetry, our experts correlate edge and application anomalies with JVM crashes, service restarts, suspicious Java child processes, unauthorized file creation, and anomalous outbound network activity. Customers should retain hs_err_pid files, application logs, reverse-proxy and WAF logs, EDR process telemetry, and container orchestrator events to support rapid triage.

Relevant Detections

Please visit the Guardian Platform to access the relevant detections for this activity, ask NEXA Detection Advisor for a breakdown of which detections are enabled in your environment, and coordinate with Deepwatch to validate logging from priority Java workloads while prioritizing remediation.

Threat Hunting Leads

  • Enumerate Oracle Java, OpenJDK, and bundled JVM builds; flag affected release lines on x86-64 hosts with AVX-512 VBMI
  • Audit Java hosts and container clusters for unexplained core dumps, hs_err_pid artifacts, or anomalous restart loops
  • Correlate java.util.Base64 decoder exceptions and malformed authentication or token requests with service failures
  • Hunt for java or javaw spawning shells, PowerShell, curl, wget, certutil, bitsadmin, or other uncommon child processes
  • Review new Java-process egress, cloud metadata service queries, suspicious file writes, and service-account privilege use
  • Confirm patched versions or mitigation flags on active processes via jcmd <PID> VM.flags after restart

Technical Artifacts 

Please visit the Guardian Platform to access available technical artifacts for this report.

Threat Object Mapping

Intrusion Set:

  • Unattributed

Attack Pattern (MITRE ATT&CK/MITRE ATLAS):

TacticTechniqueTechnique IDAssociated Threat Activity
Initial AccessExploit Public-Facing ApplicationT1190Crafted Base64 delivered to a vulnerable internet-facing Java application.
ExecutionCommand and Scripting InterpreterT1059Conditional post-exploitation behavior: compromised Java services may launch shell commands.
ImpactEndpoint Denial of Service: Application or System ExploitationT1499.004Malformed Base64 may crash the JVM or cause repeated service failure.

Vulnerabilities:

  • CVE-2026-114938

Malware/Tool:

  • No malware family is publicly associated. Public PoC reproducers, scanners and community detection rules are available; always treat third-party code as untrusted.

Additional Sources

Red Hat Security Bulletin RHSB-2026-018

CERT-EU Security Advisory 2026-021

SecurityWeek Java4Shell PoC Reporting

Sophos Java4Shell Advisory

Community Java4Shell PoC Toolkit (unverified code)

↑

Share

LinkedIn Twitter Facebook