CVE-2026-20045 IBM QRadar · QRadar

Detect CVE-2026-20045: Cisco Unified Communications Manager Code Injection in IBM QRadar

Detects exploitation attempts targeting CVE-2026-20045, a code injection vulnerability (CWE-94) in Cisco Unified Communications Manager. This KEV-listed vulnerability allows remote attackers to inject and execute arbitrary code. Detection focuses on anomalous process execution, unexpected web shell activity, and suspicious outbound connections originating from CUCM processes.

MITRE ATT&CK

Tactic
Initial Access Execution Persistence Lateral Movement

QRadar Detection Query

IBM QRadar (QRadar)
sql
SELECT
  DATEFORMAT(devicetime, 'yyyy-MM-dd HH:mm:ss') as event_time,
  sourceip,
  destinationip,
  destinationport,
  username,
  URL,
  'Process Name' as process_name,
  'Command' as command_line,
  magnitude,
  QIDNAME(qid) as event_name
FROM events
WHERE
  LOGSOURCETYPENAME(devicetype) IN ('Cisco Unified Communications Manager', 'Linux OS', 'Syslog')
  AND (
    (URL MATCHES '(?i)(/ccmadmin|/ccmservice|/cucm-uds|/axl/)'
     AND 'Request Method' = 'POST'
     AND 'Request Size' > 500)
    OR
    ("Process Name" MATCHES '(?i)(bash|sh|python|perl|wget|curl|nc)'
     AND "Parent Process" MATCHES '(?i)(java|tomcat|catalina)')
    OR
    (magnitude >= 7 AND LOGSOURCENAME(logsourceid) MATCHES '(?i)(cucm|callmanager|ucm)')
  )
  AND LAST 7 DAYS
ORDER BY magnitude DESC, event_time DESC
critical severity medium confidence

QRadar AQL query identifying CVE-2026-20045 exploitation patterns including suspicious POST requests to CUCM endpoints and shell process spawning under Java/Tomcat parent processes.

Data Sources

Cisco UCM Log SourceLinux OS Log SourceNetwork Activity

Required Tables

events

False Positives & Tuning

  • High-magnitude events from authorized CUCM administrative activities
  • Scheduled jobs that use curl/wget to interact with UCM APIs
  • Security monitoring tools that parse UCM logs and trigger on keywords

Other platforms for CVE-2026-20045


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1CVE-2026-20045 Code Injection via AXL SOAP Endpoint

    Expected signal: Tomcat access log entry showing POST to /axl/ with HTTP 200 or 500; if successful, process audit log showing command substitution execution under Tomcat user; /tmp/rce_test.txt created on CUCM host

  2. Test 2Simulate Java Spawning Reverse Shell on CUCM OS

    Expected signal: ProcessRollup2 event (CrowdStrike) or DeviceProcessEvents (MDE) showing bash or java process with parent java; network connection to ATTACKER_IP:4444 if reverse shell variant used

  3. Test 3Web Shell Deployment Simulation on CUCM Tomcat

    Expected signal: File creation event for .jsp file in /opt/cisco/platform/ui/; if Tomcat is running, subsequent HTTP GET requests to the new JSP path; audit log showing file write under test user account

  4. Test 4AXL Credential Brute-Force Reconnaissance

    Expected signal: Multiple HTTP 401/403 responses from CUCM to the source IP in rapid succession; authentication failure events in CUCM security logs; CommonSecurityLog or Syslog entries showing repeated failed logins

Unlock Pro Content

Get the full detection package for CVE-2026-20045 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections