6 Detections for Catching Java4Shell
Java4Shell corrupts memory in the HotSpot JVM's AVX-512 Base64 decoder and puts self-hosted Java apps like Keycloak, Jira and Jenkins at risk. We mapped it to 6 procedures you can detect, the 79 shipped detections behind them, and 4 exposure checks.

Java4Shell (CVE-2026-114938) is a memory-corruption bug in the OpenJDK HotSpot JVM's AVX-512 Base64 decoder that Calif disclosed on 17 November. It only affects x86-64 hosts with AVX-512 and the OpenJDK lines at risk are Java 17, 21, 25 and 27 below the November fix (OpenJDK advisory) plus a few vendor builds listed under Technical exposure.
In practice that means the self-hosted Java apps many teams run at the edge. Calif says it reached code execution before login in Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate without publishing the chains. Keycloak confirmed its own images ship an affected JDK and SonarSource published flag guidance for SonarQube. Any other Java service that decodes untrusted Base64 on an affected JVM is in the same position.
Patch now. Upgrade every affected JVM and restart it because a running JVM keeps the old code until it restarts (CERT-EU). If you can't patch a HotSpot JVM today, restart it with -XX:-UseBASE64Intrinsics or -XX:UseAVX=2 and confirm the flag took with jcmd <pid> VM.flags -all (Red Hat, Oracle jcmd).
Until every JVM is fixed, you are exposed. Use the detections below to alert and to hunt back to the day the vulnerable build first ran. GreyNoise has seen exploitation attempts and no successful intrusions on its sensors and the CVE is not in CISA's KEV catalog. Our Java4Shell threat page has the attack procedures, the logs they need and the IOCs.
Technical exposure
A HotSpot JVM is affected when the first four checks below are all true.
- The JVM is HotSpot on x86-64 (OpenJDK advisory). Upstream Java 8, Java 11 and ARM64 builds are not affected.
- The build is Java 17 from 17.0.6 or Java 21, 25 or 27 below the vendor's fix (OpenJDK advisory). The Oracle Java SE 8 Performance Pack below 8u513-perf is affected too (Red Hat).
- The host CPU has avx512f, avx512bw, avx512vbmi and bmi2 (CERT Polska). You can read them from
/proc/cpuinfoor from your cloud inventory. UseAVXis 3 or more andUseBASE64Intrinsicsis on in the running process (Oracle jcmd). Read both withjcmd <pid> VM.flags -allbecause a launch script orJAVA_TOOL_OPTIONSdoes not prove what the process is using (SonarSource).- A HotSpot JVM that matches on build and CPU with
UseAVXbelow 3 orUseBASE64Intrinsicsoff is mitigated and still needs the patch (CERT-EU). - Azul Prime is affected on Java 8, 11, 17, 21 and 25 (Azul) and Azul's fix table adds 27 (Azul Prime CVE fixes). A Prime JVM on an AVX-512 host needs 26.08.110.0 on Stable 26.08 or 26.02.510.0 on Stable 26.02 because no vendor says the HotSpot flags mitigate it.
How we built this
We built this map from public sources and vendor content. We also checked JVM telemetry in our lab, but never triggered the vulnerability there. Each shipped detection is marked repo-verified when we read the rule in a public repository and vendor-stated when we rely on the vendor's description. Each of the 9 host and exposure procedures links to the Delta Tradecraft pack where the full logic lives. The procedure at the edge has no pack entry because it only summarizes vendor controls.
At the edge
01Known-bad request filtering in front of Java servicesA managed WAF, CDN or IPS rule matches or blocks a request before the JVM handles it.1212 detections
Detection logic
If a WAF, CDN or IPS with a vendor rule for this CVE sits in front of your Java services, treat each match as a lead and not proof of an attempt. Several of these rules start in Log or Count mode so a hit may be a request that was logged and not blocked. Benign malformed traffic can also match these rules. A service with no matches is not cleared and still needs the exposure checks below.
Logs it needs
- WAF and CDN managed-rule logsneeds setuprule id or name and action
- IPS and IDS alertsneeds setupsignature id and action
- Web server access logsneeds setuprequest line and status
Shipped detections · 12
- Snort subscriber rules for CVE-2026-114938: Snort 2 SIDs 1:67502-1:67513; Snort 3 SIDs 1:301754 and 1:67502-1:67513Cisco Talos Snort subscriber and Community rulesJava4Shellvendor-statedSource ↗ (opens in a new tab)
Misses: Covers only the applications Talos identified and needs decrypted HTTP at the sensor. It sees nothing on the host and we did not read the subscriber rule text.
- OpenJDK Memory Corruption RCE (CVE-2026-114938)
Misses: Edge filtering only for traffic through Akamai. The post names the rule id and version and gives no default action or rule logic.
- AWSManagedRulesKnownBadInputsRuleSet: Java4Shell_HEADER
Misses: Inspects request headers only and ships with Count action so it logs and does not block until changed. The signature content is not published.
- AWSManagedRulesKnownBadInputsRuleSet: Java4Shell_BODY
Misses: Inspects the request body only up to 8 KB on ALB/AppSync (16 KB default and 64 KB max elsewhere) with Continue on oversize. Count action logs and does not block until changed.
- AWSManagedRulesKnownBadInputsRuleSet: Java4Shell_QUERYARGUMENTS
Misses: Inspects query argument values only and leaves out the URI path and cookies. Count action logs and does not block until changed.
- Java4Shell - Malformed Base64 Header - CVE-2026-114938
Misses: Log mode by default and header values only. It misses nested or app-unpacked data, non-HTTP traffic and traffic that bypasses Cloudflare.
- Java4Shell - Malformed Base64 Query Value - CVE-2026-114938
Misses: Log mode by default and query values only. It misses nested or app-unpacked data, non-HTTP traffic and traffic that bypasses Cloudflare.
- Java4Shell - Malformed Base64 Body Value - CVE-2026-114938
Misses: Log mode by default and body values only. It misses nested or app-unpacked data, non-HTTP traffic and traffic that bypasses Cloudflare.
- Java4Shell - Malformed Base64 Path Segment - CVE-2026-114938
Misses: Log mode by default and URL path segments only. It misses nested or app-unpacked data, non-HTTP traffic and traffic that bypasses Cloudflare.
- Java4Shell - Malformed Base64url JWT Component - CVE-2026-114938
Misses: Log mode by default and JWT components only. It misses nested or app-unpacked data, non-HTTP traffic and traffic that bypasses Cloudflare.
- Java4Shell - Malformed Base64 WebAuthn Value - CVE-2026-114938
Misses: Log mode by default and WebAuthn values only. It misses nested or app-unpacked data, non-HTTP traffic and traffic that bypasses Cloudflare.
- vpatch-CVE-2026-114938
Misses: Inspects only some headers, cookies and named parameters (not custom headers or XML/SOAP bodies) and needs an AppSec bouncer in front of the JVM.
On the host
02JVM leaves a fatal-error report or bannerA java process writes an hs_err report file or prints the JVM fatal-error banner.No rule · build itNo rule · build it
Detection logic
When a JVM crashes, it writes an hs_err_pid<pid>.log file and prints a fatal-error banner. Alert on either from a network-exposed Java service running a vulnerable build. Read the report header before you trust a file match because the file name alone does not prove a new crash. Down-rank crashes with an obvious benign cause such as an out-of-memory abort or a planned stop. A crash is a lead to investigate and not proof of exploitation.
Delta Tradecraft · DT-J4SH-HOST-002 ↗ (opens in a new tab)Logs it needs
- EDR file-create eventson by defaultcreation of hs_err_pid<pid>.log in the working directory, the temp directory or the -XX:ErrorFile path along with the image that created it. Check that your sensor records .log creates. Sysmon EID 11 or an auditd path watch needs setup.
- Container stdout and stderron by defaultthe fatal-error banner and the JRE version line. They stay on the node by default and you can search them only once a log shipper forwards them.
Shipped detections · 0
We found no shipped rule for the JVM fatal-error report or banner so you will need to build it. Collect the fatal-error banner and the JRE version line. Also collect the hs_err_pid<pid>.log path with the image that created it and the -XX:ErrorFile value from the live process where you can read it.
03Java workload or service ends on an abort and restartsA Java workload restarts after it dies on signal 6 or 11, exit code 134 or 139 or a core dump.33 detections
Detection logic
Collect every Java workload exit that ends on a signal or on an exit code of 128 plus a signal. Treat signal 6 or 11, exit code 134 or 139 or a core dump as a crash to review. Rank it lower and keep the record when you see OOMKilled, exit 3 with the JVM’s out-of-memory line, another signal or a rollout or drain within 15 minutes. A crash is a possible attempt only when the JVM is vulnerable and exposed and you find no benign cause.
Delta Tradecraft · DT-J4SH-HOST-002 ↗ (opens in a new tab)Logs it needs
- Kubernetes container statuson by defaultexit code, termination reason and restart count plus the signal where the runtime emits it
- systemd journalon by defaultEXIT_CODE and EXIT_STATUS for the unit. Core-dump records need a core-dump handler set up.
- Inbound request access logsneeds setupused with the runtime build inventory and only to rank a wave of crashes
Shipped detections · 3
- Crash analysis: process crash event with signal and hs_err_pid file retrieval
Misses: Records the crash and signal and offers the hs_err file. It opens a problem only when the crash hurts the application and does not read the report or correlate restarts.
- KubePodCrashLooping
Misses: Fires only on CrashLoopBackOff held for 15 minutes by default so aborts that recover before back-off is sampled are missed.
- Process segfaulted.
Misses: Needs a kernel segfault line and a normal HotSpot fatal error does not leave one because the JVM handles the fault and aborts. It also sees no restart.
We found no shipped rule for Java abort exits (signal 6 or 11 or exit code 134 or 139) tied to whether the JVM is vulnerable so you will need to build it.
04Server JVM starts a child it does not normally startA server JVM starts a program that the service has not started in the last 30 days.2727 detections
Detection logic
Keep a 30-day list of the child programs each Java service starts. Alert when a server JVM starts one outside that list and rank shells and download tools higher. On Linux the JDK starts a child through jspawnhelper in the same PID so match on the final program. On Windows, alert when java.exe or a service that loads jvm.dll starts cmd, PowerShell or a LOLBin. Rank build scripts and an -XX:OnError hook lower. A hit is a lead to investigate.
Delta Tradecraft · DT-J4SH-HOST-003 ↗ (opens in a new tab)Logs it needs
- EDR process creation eventson by defaultparent lineage and command line from the EDR sensor. Auditd execve, Sysmon EID 1 or Security EID 4688 with command-line capture needs setup.
- Sysmon image loadsneeds setupEID 7 loads of jvm.dll to identify a service that runs Java in-process. EID 7 is off by default so it needs setup.
Shipped detections · 27
- Suspicious Java Children Processes
Misses: The rule has test status and misses children outside its list. It does not correlate an outbound connection or a file written then executed.
- Execution:Runtime/SuspiciousShellCreated
Misses: Covers interactive shells only and leaves out script hosts and LOLBins. It has no condition that names a Java parent.
- Execution:Runtime/SuspiciousCommand
Misses: Needs a known suspicious command pattern and is not a parent-child rule so a plain Java-to-shell spawn may not fire.
- Illegitimate Shell (TRC-1016)
Misses: Needs a Tomcat JVM with a shell child because the only Java entry in the web-server name list is http-nio (Tomcat connector threads).
- Run shell untrusted
Misses: Java parents match only for named products (zookeeper, kafka, elasticsearch and others) and the tomcat macro is never_true so an arbitrary app JVM spawning a shell is missed.
- New child launched from vulnerable application (NewChildLaunchedFromVulnParent)
Misses: Fires only when the parent is flagged vulnerable and is not specific to shell or LOLBin children. We saw it only in the Log4j processes alert listing.
- New vulnerable child launched (NewVulnChildLaunched)
Misses: Needs the child itself to be a package with a known vulnerability so a shell or download tool started by the JVM matches only by coincidence.
- Possible exploitation of java based program has been detected (Preview)
Misses: Only the alert name is listed and the logic is undocumented so a JVM-spawns-shell trigger is unconfirmed.
- Webshell attacks
Misses: Built for web-shell patterns and is not specific to this CVE. A Java server spawning a plain shell child may not match.
- Execution flow hijack
Misses: A generic exploit-behaviour setting with undocumented logic so whether it fires on a JVM exploit-to-shell chain is unverified.
- Shell Execution via Java Parent Process
Misses: Needs a java parent running as uid 54321 with a working directory under /u0?/ (the Oracle E-Business Suite layout) and a shell run with -c so other Java servers are missed.
- Potential Java Service Exploitation via Suspicious Child Process
Misses: Needs a process named java to accept an inbound connection and start a listed shell, interpreter or download tool within 5 seconds so later or unlisted children are missed.
- Possible malicious web shell detected
Misses: Needs web-shell-like behavior and is listed by alert name only. It states no check for a JVM parent or a specific child.
- tomcat-8-executing-powershell
Misses: A Windows Sysrv campaign hunt that needs a tomcat* parent, an encoded cmd or PowerShell child and a further child so a single Java-to-shell event does not match.
- Suspicious Process - Java.exe Spawns Attrib.exe, Icacls.exe, or Reg.exe
Misses: Needs java.exe to start attrib.exe, icacls.exe or reg.exe on Windows so shells, download tools and Linux are missed.
- Attacker Technique - Apache Struts/Tomcat Spawns Uname
Misses: Needs a Struts or Tomcat JVM as the parent and a uname child so other Java servers, shells and other children are missed.
- Possible Java Application Webshell Process Creation Analytic (EDR, Windows)
Misses: Published for Spring4Shell and matches a java.exe parent on Windows EDR telemetry only so Linux server JVMs and Java containers are missed.
- Detection: Web or Application Server Spawning a Shell
Misses: Uses a name-based parent list so a renamed java binary, a JVM hosted in a service executable or a non-shell child (LOLBin) is missed.
- Abnormal Parent-Child Process Combination
Misses: Windows only with a parent-child baseline that names no Java parent so a match for a server JVM is unconfirmed and Linux is not covered.
- ttp_windows_webserver_process_potential_webshell_execution
Misses: Parent list is w3wp.exe, httpd.exe and tomcat.exe with a cmd.exe /c child so a Java server not run as tomcat.exe or a PowerShell child is missed.
- Shell Process Spawned by Java.EXE
Misses: Windows java.exe parent only so Linux JVMs and a JVM hosted in a service executable (jvm.dll loaded in-process) are missed.
- Generic.Detection.WebShells
Misses: Needs a Windows Tomcat parent named tomcat*.exe (default web-server list is w3wp, httpd, tomcat*, nginx) so java.exe parents and all Linux JVMs are missed.
- Possible Java Application Webshell Process Creation Analytic (Unix)
Misses: Published for Spring4Shell and needs a java parent starting a rare child on a Unix host that sends Sysmon for Linux process events.
- Shell Process Spawned by Java.EXE
Misses: Shell children of java.exe only so LOLBin or script-host children and a JVM hosted in a service executable (jvm.dll) are missed.
- Suspicious Processes Spawned by Java.EXE
Misses: The rule has test status and matches only a java.exe parent image so a renamed binary or a JVM hosted in a service executable (jvm.dll) is missed.
- Suspicious Child Process for Java - Potential Exploitation Activity
Misses: A hunting query on Windows SecurityEvent with a java.exe parent and a fixed child list so Linux JVMs and children such as curl, sh or bash are missed.
- Java Spawning Child Process by Unique Child Process Name - Potential Exploitation Activity
Misses: A manual hunt that does not alert on its own. It ranks java.exe children by rarity from Windows SecurityEvent 4688 so Linux JVM hosts are not covered.
05Unexpected child followed by a new connection or a freshly written fileA JVM’s unexpected child connects somewhere new or a file the JVM just wrote gets run.2626 detections
Detection logic
Alert on either of two sequences. First, an unexpected child is followed within 10 minutes by an outbound connection from the JVM or the child’s process tree to a destination outside its 30-day baseline. Second, a file written by the JVM or a descendant runs in the same container within 10 minutes and no unexpected child is needed. Rank lower a build child that uses a managed repository and a native helper with the product’s own hash.
Delta Tradecraft · DT-J4SH-HOST-003 ↗ (opens in a new tab)Logs it needs
- EDR process creation eventson by defaultparent lineage from EDR process creation records
- EDR network connection eventson by defaultconnections by the JVM and its children. Sysmon EID 3 needs setup. Flow logs with no process give host-level context only.
- EDR file-create eventson by defaultfiles created by the JVM and its children. Sysmon EID 11 needs setup.
Shipped detections · 26
- R0011 "Unexpected Egress Network Traffic"
Misses: Covers the connection half only and needs an external destination outside the workload’s learned profile (private ranges are skipped). It has no tie to a preceding JVM child.
- R1001 "Drifted process executed"
Misses: Covers the file half only and needs a binary that is not in the image to run. It has no tie to a Java parent or a following connection.
- Execution:Runtime/ReverseShell
Misses: Covers reverse-shell sessions only and has no Java-parent condition so download-and-run or a plain outbound connection is missed.
- Backdoor:Runtime/C&CActivity.B
Misses: Needs a destination already known as command and control. It has no tie to a Java parent or an unexpected child.
- Execution:Runtime/NewBinaryExecuted
Misses: Covers the file half in containers only and needs a newly created binary to run so a dropped script or an EC2 host is missed. It has no Java parent condition.
- Dropped Executables (dropped_executable)
Misses: Covers the file half only and needs a new executable written in a container. It has no Java parent condition and no join to an outbound connection.
- Process Standard Input Output Over Socket Detected (stdio_over_socket)
Misses: Needs a process with standard input and output on a socket (reverse-shell style) so other outbound connections are missed. It has no link to a Java parent.
- Drop and execute new binary in container
Misses: Covers the file half in containers only and is not tied to a Java parent so a host JVM dropping and running a file is not covered.
- Added Binary Executed
Misses: Covers the file half only and needs a binary that was not in the image to run. It has no link to a Java parent and no connection join.
- Detected Reverse or Bind Shell: Linux Shell Created a Network Connection
Misses: Needs a shell that opens a network connection so other unexpected children and a file written then run are missed. It has no link to a Java parent.
- Potential reverse shell detected
Misses: Only the alert name is listed and it documents no link to a Java parent or a file write-then-execute step.
- Blocked binary drift executing in the container / A drift binary detected executing in the container
Misses: Covers the file half only and fires on a binary that is not in the image once the drift policy is set to alert. It has no tie to a JVM child or a connection.
- Reverse shell attacks
Misses: Generic reverse-shell behaviour that is not keyed to a Java parent or the CVE. A Java-spawned shell without an outbound reverse connection would not match.
- Non-packaged binaries created or run by service
Misses: Keys on binaries outside a package and has no Java-specific logic. A dropped JAR or script run by the JVM or a packaged interpreter may not be flagged.
- Processes running from temporary storage
Misses: Only catches payloads run from temp paths so a file written to an application directory then executed would be missed.
- Built-in suspicious process detection: reverse shell and privilege escalation to root
Misses: Covers the reverse-shell pattern only and documents no Java-parent check or file-written-then-executed chain.
- Zero-drift file protection (new file installed and run)
Misses: Covers the file half only and blocks or flags a new file being installed and run. It has no outbound-connection join and no Java condition.
- Potential Reverse Shell via Java
Misses: Needs java.exe run with -jar from a Program Files Java jre or AdoptOpenJDK path and a cmd, PowerShell or conhost child within 1 second of a connection event.
- Possible JAVA Reverse Shell
Misses: macOS only and needs a java parent run with -jar and a bash, sh or zsh child within 5 seconds of a connection event.
- Java Drop followed by network activity
Misses: Windows only and fires when a freshly dropped Java launcher runs from a user or temp path and makes a DNS lookup. It requires no server JVM ancestor.
- Potential Reverse Shell via Java
Misses: Covers Linux JAR-launched shells only so a shell with no preceding inbound connection or a non-JAR Java launch is missed.
- Possible backdoor detected [seen multiple times]
Misses: A generic download-then-run pattern that is not tied to a Java parent and does not cover a file written by a child that never runs.
- Detected file download from a known malicious source
Misses: Needs a download from a source already known as malicious and has no tie to a JVM parent so an unknown host is not caught.
- Java Executing cmd to run Powershell
Misses: Needs java.exe to start cmd.exe with a PowerShell iex and DownloadString command line (written for Sysrv) so Linux and other children are missed.
- Outbound Network Connection from Java Using Default Ports
Misses: Needs a Java process connecting out on port 389, 636, 1099 or 1389 (Log4Shell-style) so any other port is missed and no unexpected child is required.
- IPS Rule 1005177 (Restrict Java Bytecode File (Jar/Class) Download)
Misses: Fires only if a later stage downloads Java bytecode through the inspected path. It sees no JVM ancestry, host write or execution.
06Shell or tool started inside a Java containerA shell, interpreter or download tool starts inside a Java container.1111 detections
Detection logic
In a container whose image or label names a Java service, alert on a shell, interpreter, download or recon tool. Alert when the creation process tree leads back to the JVM. Lower the priority when java is only the parent at exec time because java as the first process adopts orphans. Treat a hit with no link to the JVM as a hunt lead and lower the priority when a pods/exec audit record or probe matches. A hit is never proof of compromise.
Delta Tradecraft · DT-J4SH-HOST-003 ↗ (opens in a new tab)Logs it needs
- Container runtime process eventsneeds setupprocess events with fork lineage plus the Kubernetes pods/exec audit records and probe definitions
- EDR process creation eventson by defaultnode-level process records for hosts without a runtime sensor
Shipped detections · 11
- R0001 "Unexpected process launched"
Misses: Fires only after a baseline is learned and is not shell-specific or Java-keyed so a shell already in the learned profile is not flagged.
- Interactive shell compromise attack (correlation rule; Interactive Access group includes Interactive shell in container)
Misses: Needs an interactive, SSH or Kubernetes user-session signal plus reverse-shell, recon, evasion or persistence signals so a JVM-spawned shell alone does not fire.
- Unexpected Child Shell
Misses: Shell children only so a JVM starting curl or a script interpreter is missed. It runs in GKE Container Threat Detection only and is not Java-keyed.
- Remote Shell Execution to a Container Detected
Misses: The vendor publishes no logic so a match on a JVM-spawned shell rather than a remote exec session is unconfirmed. It is not Java-keyed and needs container logs in QRadar.
- Possible Web Shell Activity Detected
Misses: Covers web-shell-shaped invocations only so a plain interactive shell in a Java container may not match.
- Potential base64 encoded shell script execution (Preview)
Misses: Needs an encoded shell script (base64 here is script encoding and not the Base64 decoder flaw) so a plain shell start is outside what the name describes.
- Command within a container running with high privileges
Misses: A name-only listing keyed on privilege level so an unprivileged shell in a Java container is not covered.
- Shell Spawned by Java Application
Misses: Fires only when the shell has a Java ancestor so a shell from kubectl exec or a non-Java parent is not matched.
- Process profile rules (process outside the learned group profile; zero-drift)
Misses: Blind to a shell learned during Discover mode. Zero-drift allows any process from the original image so a shell already in the image passes.
- Package Management Utility in Container
Misses: Not Java-keyed and needs a package manager run inside the container so shells, interpreters and download tools are missed.
- Container Management Utility in Container
Misses: Not Java-keyed and needs a kubectl-style management command run inside the container so shells and other tools are missed.
Exposure checks
These checks find the JVMs that are affected and tell you which to patch or mitigate first. They are controls and do not detect attacker activity.
Exposure
01Live JVM runs a build below the vendor fixA running JVM whose build is older than its vendor’s Java4Shell fix.Exposure1818 detections
Detection logic
Find every running JVM by image or path and read its VM name, architecture and vendor build from the live process. Compare a HotSpot build with its own vendor’s fix and treat a package the vendor still lists as affected as unfixed. Compare Azul Prime only with the fix for its own release line. Keep batch jobs and internal-only services on the list. If you cannot read a JVM, mark it unknown and do not clear it.
Delta Tradecraft · DT-J4SH-ESTATE-001 ↗ (opens in a new tab)Logs it needs
- Per-process JVM diagnosticyou build itVM.version, VM.system_properties and VM.flags -all for each running JVM
- EDR process creation eventson by defaultexecutable path, command line and start time from the EDR sensor
- Listening-socket tableyou build itlistening sockets and the process that owns each joined to firewall or load balancer data
Shipped detections · 18
- detect-jdk-8392044.sh (Linux/macOS host detector, CVE-2026-114938 folder)
Misses: Runs the process’s binary a second time instead of querying the live JVM. Its version bounds are fixed to releases checked 2026-11-17 and it misses JVMs in macOS containers.
- Detect-Jdk8392044.ps1 (Windows host detector) and remote-jdk-8392044.ps1 (fleet run)
Misses: Starts each running JVM’s binary again instead of reading the live process. It misses a binary replaced since start and skips container JVMs and per-process environment variables.
- Vulnerability findings for CVE-2026-114938 (hosts and container images)
Misses: Host and image package scans read the disk so they miss a JVM still running an old build after an update. No query text is published for this finding.
- Runtime Vulnerability Analytics: third-party vulnerabilities for the Java runtime of running processes (resolves when the process stops or restarts, reopens if still affected)
Misses: Reads the runtime of running processes and matches it by name and version against NVD. The page does not confirm that this CVE is matched or that CPU and flags are checked.
- Oracle Java JRE CVE-2026-114938 Buffer Overflow Vulnerability (Linux, Windows, MacOS)Fortinet FortiClient / FortiGuard Endpoint VulnerabilityJava4Shellvendor-statedSource ↗ (opens in a new tab)
Misses: Checks the installed Oracle Java version on disk and does not read the live process. It cannot see Java bundled in images or appliances.
- Security Vulnerabilities in Oracle Java JDK 17.0.21.0.3, 21.0.13.0.3 (Linux, Windows, MacOS)Fortinet FortiClient / FortiGuard Endpoint VulnerabilityJava4Shellvendor-statedSource ↗ (opens in a new tab)
Misses: Checks the installed JDK version on disk and does not read the live process. It has no view of CPU flags or image layers.
- CVE-2026-114938 record in JFrog Xray and JFrog Catalog (no separate rule name published)
Misses: Reads artifacts and manifests instead of the live process. It cannot see a runtime upgraded on disk and never restarted or a JDK on a host outside any scanned artifact.
- OpenJDK Remote Code Execution Vulnerability (CVE-2026-114938) (Java4Shell)
Misses: A version-based finding read from disk that does not confirm a running JVM. It also does not check for a mismatch between disk and process or read the CPU flags.
- Memory Corruption Vulnerability in OpenJDK Base64 decoder (CVE-2026-114938) (Java4Shell)
Misses: Checks the Jenkins, Jira or Confluence application version over HTTP and never reads a JVM. The JDK build underneath, other products and CPU flags go unseen.
- Amazon Corretto 17, 21, 25 and 27 Security Update (NOV26)
Misses: Reads Corretto builds on disk and does not read the live process. Other JDK vendors need their own checks.
- Oracle Java Standard Edition (SE) November 2026 Critical Patch Update (CPUNOV2026)
Misses: A patch-level check on disk for Oracle builds only. It does not read the live process or the CPU flags.
- CVE-2026-114938 Oracle OpenJDK Java check (check ID jre-memory-corruption-rce-cve-2026-114938)
Misses: An authenticated check of the installed version on disk. It does not see the live process, bundled or container Java or the CPU flags.
- detect-jdk-8392044-aws.sh (AWS managed runtimes: Lambda, ECS/Fargate, EC2, Elastic Beanstalk, EMR)
Misses: Reads cloud service configuration instead of the live process and covers only the listed services and regions. It reports CPU as unknown on most managed hosts.
- detect-jdk-8392044-gcp.sh (GCP: Cloud Run, Cloud Run functions, App Engine, Compute Engine)
Misses: Reads cloud service configuration instead of the live process. It reports CPU as unknown on Cloud Run and Cloud Run functions so the AVX-512 path is not confirmed there.
- Remote Code Execution (RCE) in openjdk-jre | CVE-2026-114938
Misses: Reads package manifests and flags only a package-manager openjdk-jre entry. It does not see JVMs installed outside the package manager or the build a running process uses.
- Oracle Java SE Oracle CSPU Nov 2026 (Java4Shell)
Misses: Relies on the installed Oracle Java SE, GraalVM and JavaFX versions on disk. It skips non-Oracle runtimes and does not read the live process.
- Plugin 382045 (Amazon Corretto 17.x below 17.0.21.1.2)
Misses: A version-based plugin for the installed Corretto 17 build only. It reads the disk and does not read the live process.
- KQL Java inventory, binary locations and internet-facing listenersThreat Defence KQL hunts for Sentinel and DefenderJava4Shellvendor-statedSource ↗ (opens in a new tab)
Misses: Lists internet-facing listeners from inventory with version-only logic. It does not read the build of the live process.
02Java runtimes hiding in images and bundled productsJava runtimes on hosts, in container images and inside bundled products that package lists miss.Exposure88 detections
Detection logic
Search hosts and each image’s merged filesystem for the release file, the java binary and the modules file because package names miss bundled runtimes. Join the image digest to running containers because a tag can show a newer build than the container runs. Rank lower an image that nothing runs and a JDK that sits only in a build stage or a deleted layer. Each runtime you find still needs the per-process check before you call it vulnerable.
Delta Tradecraft · DT-J4SH-ESTATE-001 ↗ (opens in a new tab)Logs it needs
- Container image and SBOM inventoryyou build itthe image digest of each running container plus the release file and java binary in the image’s merged filesystem
- EDR process creation eventson by defaultexec records that map a runtime to a running process
Shipped detections · 8
- Java4Shell runtime inventory module
Misses: A community project whose link tracks the master branch so the file can change after we read it. It is inventory only and does not check the live process.
- Docker Scout vulnerability page for CVE-2026-114938 (Advisories and Impacted images)
Misses: Matches image packages and does not look at live JVMs. The page names Oracle Java SE and GraalVM builds and does not name distro OpenJDK packages.
- Container scanning (OpenJDK 17.0.6+ in images, including 21, 25 and 27)
Misses: Dependency scanning of pom.xml or build.gradle will not surface the JDK. Builds that are not OpenJDK may not be labelled as OpenJDK.
- YARA-X Java discovery content (tasks 1002, 2001, 3001, 4001; analysis 1001) plus Oracle JDK fixlets
Misses: This content is inventory and does not detect activity. The JRE 8u513 fixlets are over-tagged because standard Java 8 is not affected.
- Xray container and build-artifact JDK check with Contextual Analysis (vendor wording; no rule name published)
Misses: A JDK bundled in an image with no package metadata may not be matched. JDKs on a host outside any artifact are not covered.
- Periodic file scanning for Java runtimes
Misses: Finds OpenJDK and unused Oracle JDK installs on managed hosts. It names no container-image scanning and no discovery of Java bundled in third-party products.
- CSAM query for OpenJDK in affected version ranges (Java 17, 21, 25, 27)
Misses: Relies on the software inventory so a JDK copied into an image or app folder without a package record will not appear.
- detect-jdk-8392044.sh embedded-JVM check (libjvm.so / jvm.dll)
Misses: The check was not run on macOS. It reports only the JVMs it can locate on disk or in a running process.
03Host CPU and effective flags leave the path activeA HotSpot JVM on a CPU with AVX-512 and BMI2 that still has the Base64 path switched on.Exposure11 detection
Detection logic
For each HotSpot JVM that is below the fix or unknown, check the host or guest CPU flags for avx512f, avx512bw, avx512vbmi and bmi2 and then read the live flags with jcmd. A flag in a launch script is a lead until the live process shows it. A JVM with the path switched off is mitigated and still needs the patch. A guest whose hypervisor hides AVX-512 is not affected on that host. Azul Prime needs only avx512f and no flag is known to mitigate it.
Delta Tradecraft · DT-J4SH-ESTATE-001 ↗ (opens in a new tab)Logs it needs
- Host CPU and hardware inventoryyou build itthe flags line of /proc/cpuinfo or the CPU features from hypervisor or cloud instance inventory
- Per-process JVM diagnosticyou build itVM.flags -all for UseAVX and UseBASE64Intrinsics plus the CPU line in VM.info
Shipped detections · 1
- Detect-Jdk8392044 conditions 4 and 5 (AVX-512 VBMI/BW flags and Base64 intrinsic flags, read from a second JVM started with each running process's launch flags)
Misses: Evaluates launch options in a second JVM instead of the live process’s flags so treat it as a lead until jcmd VM.flags -all confirms. It does not parse argfiles or VMOptionsFile.
04Runtime updated on disk but the old process keeps runningA JVM that keeps running the old build after its runtime files were replaced on disk.ExposureNo rule · build itNo rule · build it
Detection logic
Look for JVMs whose runtime files show as (deleted) in /proc/<pid>/maps. That only proves a file was removed after the process started so confirm that the live build from jcmd is older than the installed build. Use the package transaction or image digest to date the update. Set aside an update to a different runtime and a reinstall of the same build. Rank lower a replica draining in a rollout. The process keeps the old build until it restarts.
Delta Tradecraft · DT-J4SH-ESTATE-001 ↗ (opens in a new tab)Logs it needs
- Live process listingyou build ita scheduled read of /proc/<pid>/maps and /proc/<pid>/exe per Java process
- Per-process JVM diagnosticyou build itVM.version for the live build
- Package and image recordsyou build itpackage transaction history or running image digests
Shipped detections · 0
We found no shipped rule for a JVM that still runs runtime files replaced on disk so you will need to build it.
Where this leaves you
Status as of 2026-11-19. Oracle and upstream OpenJDK have fixed builds at 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 (Oracle). Fixed builds are also out for Temurin 17 (17.0.21.1+2), 21, 25 and 27, Oracle GraalVM, BellSoft Liberica, SapMachine, Amazon and Microsoft, and Azul, and the pack README lists every vendor with the time of each check. Linux distributions are moving at different speeds. Ubuntu has fixed Java 17, 21 and 25 on every supported release. Debian has fixed Java 21 and 25 on trixie, but Java 17 on bookworm is still vulnerable. SUSE has fixed openSUSE Tumbleweed and its enterprise packages are still in progress. Red Hat says it is expediting fixes and had not released any. The CVE is not in CISA KEV and GreyNoise counted 192 Java4Shell-shaped requests from 6 IP addresses with 0 successful intrusions on its own sensors.
The map lists 79 shipped detections across 6 procedures and the exposure checks add 27 more across 4 controls. Every shipped detection on the host side is generic and predates Java4Shell so read what each one misses before you count it as coverage. No product we reviewed ships a rule for the JVM fatal-error report and that is the first detection we would build. The Delta Tradecraft pack has the fields, the tuning notes and the blind spots for every host and exposure procedure.




