Sigma · CVE exploitation
Java web stack: Java application server spawned a shell or download tool
- severity
- medium
- confidence
- 55/100
- generated
- 20 Nov 2026
- Linked CVE
- CVE-2026-114938
A Java process (java, javaw, Tomcat's service wrapper) started a shell, script interpreter or download tool. On an internet-facing application server that is the usual first step after remote code execution in the server or in the application it hosts. Not specific to one bug: it fires on code execution through the Java web stack by any route. Attached to the 1 CVE in this stack that skopnix reported in the last 30 days, newest CVE-2026-114938.
False-positive notes
Needs a Java process as the PARENT and a shell / interpreter / downloader as the child. Parents whose command line names Jenkins, TeamCity, Bamboo, Gradle, Maven, sbt or an IDE are excluded in Sigma and XQL (the QRadar version cannot see the parent command line, so it is louder). Any Java app that shells out still matches: run it on application servers, not build hosts, and hunt a week before alerting.
References
title: 'Skopnix - Java web stack: Java application server spawned a shell or download tool'id: acfd2ae8-b38d-5adf-8c12-af92817eb067status: experimentaldescription: 'A Java process (java, javaw, Tomcat''s service wrapper) started a shell, script interpreter or download tool. On an internet-facing application server that is the usual first step after remote code execution in the server or in the application it hosts. Not specific to one bug: it fires on code execution through the Java web stack by any route. Attached to the 1 CVE in this stack that skopnix reported in the last 30 days, newest CVE-2026-114938.'references: - https://skopnix.com/cve/CVE-2026-114938author: skopnixdate: '2026-11-20'tags: - attack.execution - attack.t1190 - attack.t1059.004 - attack.t1059.003 - attack.t1505.003 - cve.2026-114938logsource: category: process_creationdetection: selection_parent: ParentImage|re|i: '[/\\](java|javaw|tomcat[0-9]*w?)(\.exe)?$' selection_child: Image|re|i: '[/\\](sh|bash|dash|zsh|ksh|busybox|curl|wget|nc|ncat|netcat|socat|perl|python[0-9.]*|cmd\.exe|powershell\.exe|pwsh\.exe|certutil\.exe|bitsadmin\.exe|mshta\.exe|rundll32\.exe|regsvr32\.exe|wscript\.exe|cscript\.exe)$' filter_build: ParentCommandLine|contains: - jenkins - teamcity - bamboo - gradle - maven - plexus-classworlds - sbt-launch - intellij - eclipse condition: selection_parent and selection_child and not filter_buildfalsepositives: - Build and CI servers (Jenkins, TeamCity, Bamboo, Gradle / Maven daemons) start shells all day; the Sigma and XQL exclude them by parent command line - Applications that call Runtime.exec() by design (report generators, backup jobs); baseline by host and command linelevel: mediumskopnix-sigma-cve-stack-java-web-server-shell-59959dc5.yml
How to deploy on Sigma
- Step 1
- Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
- Step 2
- Run it as a hunt first: every rule ships as status experimental.
- Step 3
- Promote to an alert once a week of results is clean on your data.
- Check
- The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.