CVE-2026-20131 Elastic Security · Elastic

Detect Cisco FMC/SCC Deserialization RCE Exploitation (CVE-2026-20131) in Elastic Security

Detects exploitation of CVE-2026-20131, a deserialization of untrusted data vulnerability in Cisco Secure Firewall Management Center (FMC) and Cisco Security Cloud Control (SCC) Firewall Management. Successful exploitation allows unauthenticated or authenticated remote attackers to execute arbitrary commands on the underlying OS. This CVE is listed in CISA's Known Exploited Vulnerabilities catalog.

MITRE ATT&CK

Tactic
Initial Access Execution Lateral Movement

Elastic Detection Query

Elastic Security (Elastic)
eql
sequence by host.name with maxspan=5m
  [network where destination.port in (443, 8080, 8443)
   and host.name like~ "*fmc*" or host.name like~ "*firesight*"
   and not source.ip like "10.*" and not source.ip like "192.168.*"]
  [process where host.name like~ "*fmc*"
   and process.name in ("java", "sh", "bash", "python", "python3", "wget", "curl")
   and process.parent.name in ("java", "tomcat", "httpd", "sfmcd")]
  [file where host.name like~ "*fmc*"
   and (file.extension in ("jsp", "war", "class") or file.path like "/tmp/*" or file.path like "/var/tmp/*")]
| head 100
critical severity medium confidence

EQL sequence detection for CVE-2026-20131: correlates inbound connection to FMC, followed by suspicious child process spawned from FMC service, followed by suspicious file creation — indicative of deserialization-to-RCE chain.

Data Sources

Elastic EndpointNetwork packet captureFilebeat syslog

Required Tables

logs-endpoint.events.network-*logs-endpoint.events.process-*logs-endpoint.events.file-*

False Positives & Tuning

  • Legitimate FMC update processes spawning Java child processes
  • Scheduled backup tasks writing to /tmp on FMC appliance
  • Administrative scripts run by authorized operators post-maintenance

Other platforms for CVE-2026-20131


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 1Simulate Deserialization Payload Delivery to FMC-like Endpoint

    Expected signal: Network logs: POST to /j_spring_security_check with binary Content-Type. Process logs: java process spawning 'id' command. File creation event for /tmp/rce_proof.txt.

  2. Test 2Spawn Reverse Shell from Java Process (Post-Exploitation Simulation)

    Expected signal: ProcessRollup2 event showing java parent spawning bash child. NetworkConnectIP4 event for outbound TCP to attacker IP on port 4444.

  3. Test 3Drop Webshell on FMC Tomcat Webroot (Post-Exploitation Persistence)

    Expected signal: File creation event for .jsp file in Tomcat webroot. Syslog entry for file write by java or tomcat process user.

  4. Test 4Enumerate FMC Management API Without Authentication (Pre-Exploitation Recon)

    Expected signal: Web server access logs showing GET/POST to /api/fmc_platform/ and /api/fmc_config/ from an external IP. 401 or 200 responses logged.

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections