Interlock ransomware exploited Cisco FMC zero-day CVE-2026-20131 for 36 days before disclosure

The Interlock ransomware group exploited a maximum-severity vulnerability in Cisco Secure Firewall Management Center (FMC) as a zero-day for weeks before it was disclosed, according to Amazon’s threat intelligence team. Cisco updated its advisory on 18 March 2026 to confirm active exploitation, and CISA added the flaw to its Known Exploited Vulnerabilities catalogue the following day.

Technical details

CVE-2026-20131 (CVSS 10.0) is an insecure deserialization flaw in FMC’s web management interface. A remote, unauthenticated attacker can send crafted Java byte streams to bypass authentication and execute arbitrary Java code as root. Cisco Security Cloud Control (SCC) Firewall Management is also affected. Cisco published its advisory and fixes on 4 March, initially stating there was no known exploitation.

Amazon’s MadPot honeypot network recorded the first exploitation attempts on 26 January 2026, 36 days before disclosure. A misconfigured Interlock server then exposed the group’s toolkit. The observed chain sends crafted HTTP requests to a specific path, confirms success via an HTTP PUT to attacker infrastructure, and downloads an ELF binary hosting further tools, including: - a PowerShell reconnaissance script for Windows environments; - custom JavaScript and Java remote access trojans with SOCKS5 proxying and self-update functions; - a Bash script that turns Linux hosts into HAProxy-based relays and purges logs every five minutes; - a memory-resident web shell and a lightweight beacon; - ConnectWise ScreenConnect for persistence, Volatility for credential extraction and Certify for abusing AD CS templates.

Attribution relied on embedded ransom notes and Interlock’s Tor negotiation portal; activity timestamps suggest operators working in UTC+3. Interlock, active since September 2024, has previously hit DaVita, Kettering Health and Texas Tech University.

Who is affected

Organisations running vulnerable FMC releases with management interfaces reachable by attackers, and SCC Firewall Management customers. Compromise of FMC gives attackers control over firewall policy across the estate.

Recommendations

  • Upgrade FMC to the fixed release listed in Cisco advisory cisco-sa-fmc-rce-NKhnULJh.
  • Place FMC management on an isolated out-of-band network with no internet exposure.
  • Treat devices that were exposed between late January and patching as potentially compromised; review for unknown Java processes, cron jobs and log deletion.
  • Hunt for unauthorised ScreenConnect installations and apply Amazon’s published IOCs.

Sources