← IBM QRadar detections
IBM QRadar · CVE exploitation
Microsoft SQL Server: SQL Server spawned a shell or LOLBin
- severity
- high
- confidence
- 75/100
- generated
- 14 Nov 2026
- Linked CVE
- CVE-2026-116930 · CVE-2026-116931 · CVE-2026-116933 · CVE-2026-116937 · CVE-2026-116938 · CVE-2026-116941 · CVE-2026-116942 · CVE-2026-116944 · CVE-2026-116945 · CVE-2026-116946 · CVE-2026-116947 · CVE-2026-118106 · CVE-2026-118112 · CVE-2026-67372 · CVE-2026-67374 · CVE-2026-67391 · CVE-2026-67632 · CVE-2026-67637 · CVE-2026-67646 · CVE-2026-88111 · CVE-2026-94511 · CVE-2026-94513
- Requires
- Process-creation events with the parent in "Parent Process Name" (Sysmon event 1, or 4688 with command-line auditing).
sqlservr.exe started cmd, PowerShell, a script host or a download / proxy-execution LOLBin. Not specific to one bug: it fires on code execution through the Microsoft SQL Server by any route. Attached to the 22 CVEs in this stack that skopnix reported in the last 30 days, newest CVE-2026-118112, CVE-2026-118106, CVE-2026-116947.
False-positive notes
Needs sqlservr.exe as the PARENT and one of cmd, PowerShell, pwsh, wscript, cscript, mshta, rundll32, regsvr32, certutil, bitsadmin, whoami or curl as the child. SQL Agent jobs run under sqlagent.exe and do not match. Instances that use xp_cmdshell by design will: baseline first.
References
- skopnix.com/cve/CVE-2026-118112 ↗
- skopnix.com/cve/CVE-2026-118106 ↗
- skopnix.com/cve/CVE-2026-116947 ↗
- skopnix.com/cve/CVE-2026-116946 ↗
- skopnix.com/cve/CVE-2026-116945 ↗
- skopnix.com/cve/CVE-2026-116944 ↗
- skopnix.com/cve/CVE-2026-116942 ↗
- skopnix.com/cve/CVE-2026-116941 ↗
- skopnix.com/cve/CVE-2026-116938 ↗
- skopnix.com/cve/CVE-2026-116937 ↗
- skopnix.com/cve/CVE-2026-116933 ↗
- skopnix.com/cve/CVE-2026-116931 ↗
- skopnix.com/cve/CVE-2026-116930 ↗
- skopnix.com/cve/CVE-2026-94513 ↗
- skopnix.com/cve/CVE-2026-94511 ↗
- skopnix.com/cve/CVE-2026-88111 ↗
- skopnix.com/cve/CVE-2026-67646 ↗
- skopnix.com/cve/CVE-2026-67637 ↗
- skopnix.com/cve/CVE-2026-67632 ↗
- skopnix.com/cve/CVE-2026-67391 ↗
- skopnix.com/cve/CVE-2026-67374 ↗
- skopnix.com/cve/CVE-2026-67372 ↗
SELECT DATEFORMAT(starttime, 'yyyy-MM-dd HH:mm:ss') AS event_time, LOGSOURCENAME(logsourceid) AS log_source, sourceip, username, "Process Path", "Process Name", "Command"FROM eventsWHERE ("Parent Process Name" ILIKE '%sqlservr.exe' AND ("Process Name" ILIKE '%cmd.exe' OR "Process Name" ILIKE '%powershell.exe' OR "Process Name" ILIKE '%pwsh.exe' OR "Process Name" ILIKE '%wscript.exe' OR "Process Name" ILIKE '%cscript.exe' OR "Process Name" ILIKE '%mshta.exe' OR "Process Name" ILIKE '%rundll32.exe' OR "Process Name" ILIKE '%regsvr32.exe' OR "Process Name" ILIKE '%certutil.exe' OR "Process Name" ILIKE '%bitsadmin.exe' OR "Process Name" ILIKE '%whoami.exe' OR "Process Name" ILIKE '%curl.exe'))AND LOGSOURCETYPENAME(devicetype) IN ('Microsoft Windows Security Event Log')LAST 7 DAYSskopnix-qradar-cve-stack-mssql-sqlservr-shell-b49de25c.aql
How to deploy on IBM QRadar
- Step 1
- Create the reference set from its spec (Reference Data API, or Admin > Reference Set Management) and schedule the skopnix feed load.
- Step 2
- Paste the AQL into Log Activity > Advanced Search to hunt the last seven days.
- Step 3
- For alerting, build the CRE rule from the test stack shown and exclude your known-good building block.
- Check
- Custom properties ("URL Host", "URL", "File Hash", "Process CommandLine") come from your DSMs and content extensions; rename them if yours differ.