CVE-2026-20131 — Interlock Ransomware Exploiting Cisco Secure Firewall Management Center RCE
Executive Summary
CVE-2026-20131 is a CVSS 10.0 remote-code-execution flaw in Cisco Secure Firewall Management Center (FMC). The web-based management interface insecurely deserializes a user-supplied Java byte stream, allowing an unauthenticated attacker to execute arbitrary Java code as root via crafted HTTP requests. FMC is the centralized brain for an organization's Cisco firewall estate, so root on it is a strategic foothold.
The Interlock ransomware group exploited this as a zero-day from 2026-01-26 — roughly 36 days before Cisco's official disclosure on 2026-03-04 — per Amazon threat-intelligence and eSentire reporting. Post-exploitation, the actor runs multi-stage intrusions: reconnaissance, payload deployment and persistence, abusing legitimate tooling including ScreenConnect RMM, the Volatility memory-forensics suite (credential / memory access), and the offensive AD-CS tool Certify. Targeted sectors include education, engineering / architecture / construction, manufacturing, healthcare and government.
Source Review & Web Hunter Notes
| Tier | Source | Key Finding | Carry |
|---|---|---|---|
| 1 · Vendor (PSIRT) | Cisco Security Advisory — CVE-2026-20131 | Insecure Java deserialization on FMC web UI; unauth RCE as root; fixed release 2026-03-04 | yes |
| 1 · Vendor research | Amazon (AWS) Threat Intelligence | Identified the active Interlock campaign targeting enterprise firewalls via this flaw | yes |
| 1 · Vendor research | eSentire — CVE-2026-20131 exploited by Interlock | Crafted HTTP requests to FMC web mgmt; multi-stage intrusion; ScreenConnect / Volatility / Certify abuse | yes |
| 1 · News of record | The Hacker News — Interlock exploits Cisco FMC zero-day for root | Zero-day since 2026-01-26, 36 days before disclosure; root access; sectors targeted | yes |
| 2 · Vendor research | Recorded Future / Hive Pro / Help Net Security | March 2026 CVE landscape; FMC zero-day exploited weeks before patch; CVSS 10.0 | partial |
| 2 · Vendor research | Security Affairs / SecPod | Early-access exploitation timeline; deserialization root-cause detail | partial |
Decisions: lead with the upgrade (the Cisco fixed release closes the RCE). The appliance is off-sensor, so durable detections are (a) FMC web/admin log hunts where ingested and (b) endpoint hunts for Interlock's hands-on-keyboard tooling, which is the more reliable signal in most Falcon estates. Key on tooling/behavior (ScreenConnect, Certify, recovery inhibition, encryption) since exploit-stage atomic IOCs are perishable and not fully public — pull live IOCs from the eSentire / Amazon / Cisco advisories.
Hunt Brief & Attack Chain
Working hypothesis: An attacker sends crafted HTTP requests to an internet-reachable Cisco Secure FMC web interface, triggers insecure Java deserialization, and gains root code execution. From that foothold Interlock pivots into the managed network, deploys ScreenConnect for hands-on access, uses Certify / Volatility for credential and AD-CS abuse, inhibits recovery, and deploys ransomware for double extortion.
| Step | Behavior | Telemetry | Hunt Angle |
|---|---|---|---|
| 1 · Exploit FMC | Crafted HTTP request → insecure Java deserialization → root code exec (CVE-2026-20131) | FMC web/admin logs | Q1, Q2; Native N2 |
| 2 · Establish access | Deploy ScreenConnect / RMM for interactive control on internal hosts | ProcessRollup2, NetworkConnectIP4 | Q3 |
| 3 · Credential / AD-CS abuse | Certify (AD-CS), Volatility (memory) for credential and certificate theft | ProcessRollup2 | Q4 |
| 4 · Recon + lateral | AD/host enumeration, lateral movement to high-value systems | ProcessRollup2, UserLogon | Baseline; N4 |
| 5 · Inhibit recovery | Shadow-copy / backup / recovery deletion before encryption | ProcessRollup2 | Q5 |
| 6 · Impact | High-volume file encryption, ransom note, double-extortion leak | FileCreateInfo | Q6; §11 |
Affected surface & telemetry
| Surface | Required Telemetry | Priority | Gap Risk |
|---|---|---|---|
| Internet-reachable Cisco Secure FMC web UI | FMC version inventory + web/admin access logs ingested | Critical | High — appliance off-sensor; depends on log forwarding |
| RMM / remote-access tooling | Process exec + network (ProcessRollup2, NetworkConnectIP4) | High | Low — standard Falcon sensor |
| AD-CS / credential abuse | Process exec + command line (ProcessRollup2) | High | Medium — renamed tooling evades name match |
| Recovery inhibition / encryption | Process + file ops (ProcessRollup2, FileCreateInfo) | High | Low — standard Falcon sensor |
Consolidated IOC Table
| Type | Value | Conf | Action | Context |
|---|---|---|---|---|
| Version | Cisco Secure FMC below the 2026-03-04 fixed release | high | detect | Vulnerable to CVE-2026-20131 — upgrade closes it |
| Behavior | Anomalous deserialization-style POST to FMC web mgmt + root process spawn | medium | hunt | Exploitation signature (log-dependent) |
| Tool | ScreenConnect / unsanctioned RMM on internal hosts | high | detect | Interlock interactive access |
| Tool | Certify.exe / AD-CS abuse; Volatility on production hosts | high | detect | Credential / certificate theft |
| Behavior | vssadmin/wbadmin/bcdedit recovery deletion → mass file write | high | detect | Interlock pre-encryption kill-chain |
ATT&CK Mapping
| Tactic | Technique | Observed Behavior | Query / Control |
|---|---|---|---|
| Initial Access | T1190 — Exploit Public-Facing Application | Insecure deserialization RCE on the FMC web UI | Q1, Q2; S10 upgrade |
| Execution | T1059 — Command and Scripting Interpreter | Arbitrary Java code as root post-deserialization | Q2 |
| Persistence / C2 | T1219 — Remote Access Software | ScreenConnect / RMM for hands-on access | Q3 |
| Credential Access | T1649 — Steal or Forge Authentication Certificates | Certify abuse against AD-CS | Q4 |
| Credential Access | T1003 — OS Credential Dumping | Volatility for memory/credential extraction | Q4 |
| Impact | T1490 / T1486 — Inhibit Recovery / Data Encrypted | Shadow deletion then encryption | Q5, Q6; §11 |
Native Audit-Log Hunts
| Hunt | Source | Logic | Response |
|---|---|---|---|
| N1 · FMC version / patch inventory | Cisco FMC / asset inventory | FMC instances below the 2026-03-04 fixed release, especially internet-reachable web UIs | Upgrade to the fixed release — the fix |
| N2 · FMC web/admin log review | FMC system & audit logs | Anomalous POSTs to the web mgmt interface, unexpected admin/root actions since 2026-01-26 (zero-day window) | Per Cisco/eSentire guidance; pivot to endpoint hunts |
| N3 · Sanctioned-RMM allow-list review | Software inventory / EDR | ScreenConnect or other RMM present on hosts where it is not sanctioned | Investigate; remove; scope access |
| N4 · AD-CS abuse review | AD-CS / Windows Security logs (4886/4887) | Unusual certificate enrollment / template abuse following the FMC window | Correlate with Q4; revoke abused certs |
CrowdStrike LogScale CQL Hunt Queries
⚠ validate in your tenant. Q3–Q6 are Falcon-sensor endpoint hunts (fields validated against the Falcon event reference) covering the Interlock post-exploit kill-chain.Looks for: unauthenticated POST requests to FMC web-management endpoints carrying serialized-object-style payloads (Java rO0 base64 marker, large bodies, odd content types). ⚠ field names parser-dependent
// HUNT: Anomalous deserialization-style POST to the Cisco FMC web UI (CVE-2026-20131) // MITRE: T1190 | CONF: medium FP: medium COST: low // REQUIRES: Cisco FMC web/admin/HTTP logs ingested into LogScale/NG-SIEM // FALSE POSITIVES: legitimate large admin POSTs / API automation // TUNING: scope to the FMC mgmt VIP; baseline known API clients; alert on unauth + rO0 marker vendor=/cisco/i product=/Firewall Management Center|FMC/i | http_method="POST" | url=/\/(api|admin|ui|webui)\//i | (request_body=/rO0[AB]/ OR content_type=/application\/x-java-serialized-object/i OR body_len > 50000) | auth_status=/fail|none|anonymous/i | table([@timestamp, src_ip, http_method, url, content_type, body_len, user_agent], limit=200) | sort(@timestamp, order=desc)
Looks for: shell / network-tool execution as root on the FMC host correlated to the web service — the post-deserialization payload. ⚠ field names parser-dependent
// HUNT: Root shell / outbound tooling on the FMC appliance after web-UI activity // MITRE: T1190, T1059 | CONF: medium FP: low-med COST: low // REQUIRES: FMC OS/syslog (auth, process, or audit) ingested // FALSE POSITIVES: sanctioned maintenance windows / Cisco TAC sessions // TUNING: allow-list scheduled maintenance; alert on shells parented by the web/Java service vendor=/cisco/i host=/fmc/i | user=/root/i | process=/(bash|sh|curl|wget|nc|ncat|python|perl)$/i | parent_process=/(java|tomcat|httpd|nginx|mojo)/i | table([@timestamp, host, user, process, parent_process, cmdline], limit=200) | sort(@timestamp, order=desc)
Looks for: ScreenConnect / common RMM binaries executing on internal hosts. FP: sanctioned IT RMM — allow-list your approved tool and management hosts.
// HUNT: Unsanctioned RMM / remote-access software (Interlock hands-on access) // MITRE: T1219 | CONF: high FP: medium COST: low // REQUIRES: ProcessRollup2 // FALSE POSITIVES: the org's sanctioned RMM tool / IT admin hosts // TUNING: allow-list the approved RMM product + its deployment hosts; alert on the rest #event_simpleName=/ProcessRollup2|SyntheticProcessRollup2/ | FileName=/^(ScreenConnect|Connectwisechat|AnyDesk|atera|splashtop|ScreenConnect\.ClientService|ScreenConnect\.WindowsClient)\.exe$/i | table([@timestamp, ComputerName, UserName, FileName, CommandLine, ParentBaseFileName, SHA256HashData], limit=200) | sort(@timestamp, order=desc)
Looks for: offensive AD-CS tooling (Certify) and memory-forensics (Volatility) on production hosts, plus their tell-tale command-line verbs. FP: sanctioned red-team / IR — allow-list.
// HUNT: Certify / Volatility credential & certificate-theft tooling on production hosts // MITRE: T1649, T1003 | CONF: high FP: low COST: low // REQUIRES: ProcessRollup2 // FALSE POSITIVES: sanctioned red-team / IR engagements — allow-list operator hosts/AIDs #event_simpleName=/ProcessRollup2|SyntheticProcessRollup2/ | (FileName=/^(Certify|vol|volatility|volatility3)\.exe$/i OR CommandLine=/certify\s+(find|request|enroll)|--vulnerable|windows\.pslist|windows\.lsadump/i) | table([@timestamp, ComputerName, UserName, FileName, CommandLine, ParentBaseFileName, SHA256HashData], limit=200) | sort(@timestamp, order=desc)
Looks for: shadow-copy, backup-catalog and boot-recovery deletion — the Interlock pre-encryption step. Accomplishes: high-fidelity ransomware staging detection independent of the FMC entry path.
// HUNT: Volume shadow / backup / recovery deletion ahead of encryption (Interlock kill-chain) // MITRE: T1490 | CONF: high FP: low COST: low // REQUIRES: ProcessRollup2 command-line telemetry // FALSE POSITIVES: sanctioned backup maintenance — allow-list backup service accounts #event_simpleName=/ProcessRollup2|SyntheticProcessRollup2/ | FileName=/^(vssadmin|wmic|bcdedit|wbadmin|powershell|cmd)\.exe$/i | CommandLine=/(delete\s+shadows|shadowcopy\s+delete|resize\s+shadowstorage|deletecatalog|recoveryenabled\s+no|bootstatuspolicy\s+ignoreallfailures)/i | table([@timestamp, ComputerName, UserName, FileName, CommandLine, ParentBaseFileName], limit=200) | sort(@timestamp, order=desc)
Looks for: one process touching an abnormally high number of distinct files in a short window — the encryption burst. FP: backup/indexing/AV — allow-list. Pair with Q5 on the same host for confidence.
// HUNT: Single process performing high-volume file modification (ransomware encryption burst) // MITRE: T1486 | CONF: medium FP: medium COST: medium // REQUIRES: FileCreateInfo / file-write telemetry with writing-process context // FALSE POSITIVES: backup agents, search indexers, AV — allow-list by process // TUNING: tune the threshold to your environment; correlate with Q5 hits on same aid #event_simpleName=/PeFileWritten/ | FileName!=/^(Backup|SearchIndexer|CSFalconService|MsMpEng)\.exe$/i | groupBy([aid, ContextProcessId, ContextBaseFileName], function=([ count(TargetFileName, distinct=true, as=filesTouched), min(@timestamp, as=t0), max(@timestamp, as=t1) ])) | filesTouched >= 200 | sort(filesTouched, order=desc)
CrowdStrike Custom IOA Recommendations
| IOA Name | Field Patterns | Benign Exclusions | Deployment Path |
|---|---|---|---|
| Interlock — AD-CS theft tooling | Image Certify.exe or CmdLine certify find/request / --vulnerable | Sanctioned red-team operator hosts (excluded) | Endpoint Security → Custom IOA → Process Creation (Detect+Block) |
| Interlock — Recovery inhibition | Child vssadmin/wbadmin/bcdedit.exe; CmdLine delete shadows / recoveryenabled no | Sanctioned backup service accounts (excluded) | Custom IOA → Process Creation (Detect+Block) |
Machine-Readable IOC Appendix
Grouped IOC Quick-Copy
One-click blocks for version audit, behavioral detection and tooling allow-listing. The Cisco fixed release is the control; behavior + tooling are the durable detections. No complete public atomic IOC set was released — pull live exploit IOCs from the eSentire / Amazon / Cisco advisories.
Anonymous deserialization-style POST to the FMC web mgmt interface (rO0 marker / java-serialized) Root shell or curl/wget/nc parented by the FMC web/Java service ScreenConnect / unsanctioned RMM executing on internal hosts Certify (AD-CS) or Volatility (memory) tooling on production hosts vssadmin/wbadmin/bcdedit recovery-deletion commands (Interlock pre-encryption) One process modifying 200+ distinct files in under a minute (encryption burst)
# Cisco Secure FMC — confirm patched against CVE-2026-20131 # 1) Identify FMC software version (Help > About / System > Configuration) # 2) Upgrade to the Cisco fixed release referenced in the 2026-03-04 advisory # 3) Restrict the FMC web-management interface to a management network ONLY # - never expose the FMC web UI to the internet # 4) Review FMC audit logs back to 2026-01-26 (zero-day window) for prior compromise # Reference: Cisco Security Advisory CVE-2026-20131 (CVSS 10.0)
# Interlock hands-on-keyboard tooling to allow-list (sanctioned) or block (unexpected) ScreenConnect / ConnectWise Control # RMM — keep ONLY your approved tool AnyDesk / Atera / Splashtop # other RMM seen in extortion intrusions Certify.exe # offensive AD-CS abuse — block on production volatility / vol.py # memory forensics — block outside IR hosts # Enforce: application control / RMM allow-listing; alert on any RMM not on the list
CVE-2026-20131 # Cisco Secure FMC insecure-deserialization RCE (this pack) — CVSS 10.0 Interlock # ransomware group; double extortion; exploited the FMC zero-day # Timeline: zero-day exploitation since 2026-01-26; Cisco disclosure 2026-03-04 # Live IOCs: pull from eSentire / Amazon (AWS) Threat Intelligence / Cisco advisories # Defense-in-depth: isolate FMC mgmt plane; RMM allow-listing; AD-CS hardening
Hardening — Tiered & Deployable
This one is patchable — upgrading FMC is the fix. The rest isolates the management plane and removes the Interlock hands-on toolkit's room to operate.
- Upgrade Cisco Secure FMC to the fixed release (per the 2026-03-04 advisory) — M1051. Closes CVE-2026-20131.
- Remove the FMC web-management interface from internet exposure — M1030 / M1035. Restrict to a dedicated management network / jump host.
- Review FMC audit logs back to 2026-01-26 — M1047. Confirm no prior zero-day compromise before declaring closed.
- RMM allow-listing — block all RMM except the sanctioned tool — M1038 / M1042. Defeats the ScreenConnect hands-on stage (Q3).
- Harden AD-CS against Certify-style abuse — M1042 / M1018. Remove ESC-vulnerable templates; enforce manager approval; restrict enrollment agents.
- Application control to block offensive tooling on production — M1038. Stops Certify / Volatility outside sanctioned IR hosts (Q4).
- Tamper-protected, offline / immutable backups — M1053. Neutralizes recovery inhibition (Q5).
- Segment management of network appliances — M1030. A root foothold on FMC can't pivot freely into production.
- Out-of-band management plane for all security appliances — M1030. Isolate FMC/FTD admin from user networks.
- Continuous appliance version & config-drift monitoring — M1016. Alert when an appliance falls behind on PSIRT fixes or re-exposes its web UI.
- Default-deny application control + tiered admin model — M1038 / M1018. Raises cost across the whole Interlock kill-chain.
Containment Runbook
| Phase | Actions | Owner | Evidence |
|---|---|---|---|
| Isolate | Restrict FMC mgmt access to a break-glass admin path; network-contain internal hosts running unsanctioned RMM or showing Q4/Q5 hits | Network + SOC L2 | Q3–Q5 rows; FMC access log |
| Triage | Pull FMC audit logs (2026-01-26 →) for exploitation; map RMM / Certify / Volatility execution and any recovery-deletion activity on endpoints | SOC L2 | FMC logs; Q3–Q6 rows |
| Eradicate | Remove planted RMM and tooling; revoke certificates abused via AD-CS; reset credentials harvested via memory/AD-CS; rebuild FMC if root compromise confirmed | IR | Cert / cred revocation log |
| Recover | Restore from offline backups if encryption occurred; bring FMC up only on the fixed release behind the mgmt network; rotate privileged credentials | IR + IT | Restore log; FMC version readout |
| Harden | RMM allow-listing; AD-CS template hardening; promote Q4/Q5 IOAs; enable appliance config-drift monitoring (§10) | Detection Eng | Policy state; IOA enabled |
Detection Coverage Map & Validation
| Technique | Behavior | CQL | IOA | Coverage |
|---|---|---|---|---|
| — | Vulnerable FMC version / exposed web UI | — | — | Good upgrade + N1/N2 audit |
| T1190 / T1059 | FMC deserialization exploitation | Q1, Q2 | — | Partial needs FMC logs ingested |
| T1219 | RMM / ScreenConnect hands-on access | Q3 | — | Partial Detect-only; allow-list first |
| T1649 / T1003 | Certify / Volatility credential theft | Q4 | IOA-1 | Good |
| T1490 | Recovery inhibition | Q5 | IOA-2 | Good |
| T1486 | Encryption burst | Q6 | — | Partial threshold-tuned |
Validation gates: (1) confirm Cisco FMC logs are ingested and the parser field names in Q1–Q2 resolve in your tenant; (2) allow-list your sanctioned RMM before enabling Q3 alerting; (3) Q4/Q5 return zero hits in a 30-day benign lookback; (4) tune the Q6 filesTouched threshold against a benign baseline; (5) inventory FMC versions (N1) and confirm the fixed release + that the web UI is off the internet; (6) promote Q4/Q5 to Custom IOA Detect+Block (target FP < 1/week).
Hunt Summary Ticket
TITLE: Hunt — CVE-2026-20131 (Interlock / Cisco Secure FMC Deserialization RCE)
SEVERITY: Critical (Exploited ITW, CVSS 10.0, unauth root RCE; Interlock ransomware)
SCOPE: Cisco Secure FMC (web UI) + internal endpoints reached post-exploit
HYPOTHESIS: Attacker sends crafted HTTP requests to the FMC web UI, triggers insecure Java
deserialization for root code exec, then deploys ScreenConnect, abuses AD-CS via
Certify, inhibits recovery and encrypts (Interlock double extortion).
QUERIES RUN: Q1 FMC deserialization POST | Q2 FMC root shell | Q3 unsanctioned RMM |
Q4 Certify/Volatility (IOA) | Q5 recovery inhibition (IOA) | Q6 encryption burst
+ Native N1-N4 (FMC version, FMC log review, RMM allow-list, AD-CS abuse)
DO FIRST: Upgrade FMC + remove web UI from internet; then Q4, Q5 -> escalate hits
FINDINGS: <pending analyst execution>
GAPS: Q1-Q2 depend on Cisco FMC logs being ingested; parser field names vary
ACTIONS: Patch FMC; isolate mgmt plane; RMM allow-listing; AD-CS hardening;
promote Q4/Q5 to Custom IOA Detect+Block
OWNER: HuntPack
VERSION: v0.1 - 2026-06-13
Changelog
table() calls now carry an explicit row limit: the default is 200 and truncation is silent, so a capped result was indistinguishable from a complete one. Atomic-IOC sweeps (filters over 5+ hashes or C2 IPs) use limit=max so a wide infection is never silently under-scoped; behavioural hunts use limit=200, where exceeding the cap indicates the query needs tuning. Where present, event names that do not exist in the Falcon data model were corrected (e.g. ServiceInstalled is a Sysmon concept, not a Falcon event; ElfFileWritten is ELFFileWritten) — such queries could never return a row. No detection logic, fields, or IOCs changed.References
| Tier | Source | Used For |
|---|---|---|
| 1 | Amazon (AWS) Threat Intelligence — Interlock targeting enterprise firewalls | Campaign identification, FMC targeting, IOCs |
| 1 | eSentire — CVE-2026-20131 exploited by Interlock | Crafted-HTTP exploitation, ScreenConnect / Volatility / Certify tooling |
| 1 | The Hacker News — Interlock exploits Cisco FMC zero-day for root | Root RCE, zero-day timeline (2026-01-26), targeted sectors |
| 2 | Help Net Security — Cisco FMC flaw exploited weeks before patch | Disclosure timeline, exposure, CVSS 10.0 |
| 2 | Hive Pro — CVE-2026-20131 threat advisory | Deserialization root-cause, mechanism |
| 2 | Recorded Future — March 2026 CVE landscape | Context; Interlock FMC zero-day in the monthly landscape |
HuntPack v0.1 · CVE-2026-20131 (Interlock / Cisco Secure FMC RCE) · Generated 2026-06-13 · Defensive use only — no exploit code. The fix (upgrade FMC to the Cisco fixed release + remove the web UI from the internet) closes the RCE; the hunts are detection & defense-in-depth for the Interlock post-exploit kill-chain. Q1–Q2 field names depend on your Cisco FMC log parser — validate in your tenant before alerting.