Monday 16 November 2026
Security

Interlock exploited Cisco's FMC RCE flaw for over five weeks before a patch

The deserialization bug in Cisco Secure Firewall Management Center was fixed on March 4, but Amazon had seen Interlock using it since January 26. Affected firewalls need a compromise review, not just a patch.

Building 10 of the Cisco San Jose Main Campus, executive headquarters offices
Building 10 at Cisco's San Jose headquarters campus, where the company is based. Photograph: Travis Wise/Wikimedia Commons (CC BY 2.0)

Cyber Kendra reported on Sunday that Interlock ransomware operators were exploiting a critical Cisco Secure Firewall Management Center deserialization bug for more than five weeks before a patch arrived. CVE-2026-20131 stems from insecure deserialization, CWE-502, in the web management interface of FMC; Cisco assigns a CVSS score of 10.0, letting an unauthenticated remote attacker execute arbitrary Java code as root. FMC is the console that distributes policy to an organisation's entire set of Cisco firewalls, so gaining root on that one system reaches every managed device. Cisco fixed and announced the weakness on March 4, 2026.

Amazon threat intelligence later reported that its honeypot network recorded Interlock exploiting it since January 26. A technical analysis from SecureLayer7 reconstructs the attack from the public proof-of-concept and Amazon's telemetry. By November 15, every supported on-premises FMC branch had a fixed release, and Cisco had already updated its hosted Security Cloud Control Firewall Management service; no workaround is available from Cisco. CISA has added the flaw to its Known Exploited Vulnerabilities catalog and noted that ransomware operators are known to use it.

How the attack works

Java serialization turns an object into a byte stream, and deserialization rebuilds it. The FMC web interface accepts that byte stream and reconstructs the object without verifying the sender or validating the contents. An attacker transmits an HTTP POST with a serialized Java object in the request body; the object begins with the byte sequence AC ED 00 05. When the server rebuilds the object, a gadget chain hidden inside it, made from legitimate library classes arranged to run a command, executes before any application-level validation. The FMC web services already run with root privileges, so the command does too.

According to SecureLayer7, the observed payloads follow the output format of ysoserial, a public tool for creating such chains; Zscaler's detection relies on a ysoserial signature. The exact FMC endpoint, gadget chain, and Cisco's code fix have not been published. SecureLayer7 states it did not run the exploit and its sequence is a reconstruction. Cisco's Advanced Security Initiatives Group discovered the flaw during internal security testing and tracks it as bug CSCwt14636. The CVE record identifies impacted FMC versions in the 6.4 and 7.x series through 7.7.11, plus 10.0.0. Secure Firewall ASA and Secure Firewall Threat Defense software are unaffected.

What Interlock did after getting root

Amazon's sensors saw requests to a specific FMC path carrying Java code and two URLs. One URL supplied configuration data for the exploit; the other told the compromised FMC to send an HTTP PUT with a generated file to an attacker's server, which confirmed to Interlock that the exploit succeeded. Amazon's researchers responded with the PUT that the attackers wanted to receive, pretending to be a compromised appliance. The attacker's server returned an ELF executable, and that same poorly secured staging host held the group's full toolkit, arranged in per-target folders. CJ Moses, CISO of Amazon Integrated Security, said Interlock “had a zero-day in their hands.”

The toolkit included a PowerShell script that inventories Windows hosts, two remote access trojans, a memory-resident Java web shell that executes AES-128-encrypted commands without writing to disk, and a Bash script that converted Linux servers into HAProxy relays and installed a cron entry that erases logs every five minutes. The group also used ConnectWise ScreenConnect, Volatility and Certify. Amazon linked the activity to Interlock using the ransom note, the TOR negotiation portal, and a unique organisation identifier for each victim. Education was the most targeted sector, followed by engineering and construction, manufacturing, healthcare, and government. Based on timing, the operators likely operate in UTC+3, with a 75 to 80 percent degree of confidence.

Cisco updated its advisory on March 18 to confirm active exploitation, and CISA listed CVE-2026-20131 in its Known Exploited Vulnerabilities catalog on March 19, giving US federal agencies until March 22 to remediate. Zscaler ThreatLabz recorded attempts beginning March 6, two days after the patch, aimed at U.S. technology and software companies; it said the payloads included a proof-of-concept from GitHub. Several repositories now claim to offer scanners or exploits; exploit trackers have marked at least one as a Trojan that targets its downloaders. As of October 15, SecureLayer7 gives the flaw an EPSS score of 0.432, which tops 98.7 percent of all scored CVEs; it also cites internet scans showing about 300 to 700 FMC management interfaces exposed online.

FMC has had three exploited flaws in 2026. CVE-2026-20079, an authentication bypass also rated 10.0 and patched the same day, and CVE-2026-20316, a hard-coded low-privilege account disclosed July 29. On September 9, Cisco Talos reported that three distinct clusters, including an affiliate of Qilin ransomware and a group believed to be state-backed, were abusing those two vulnerabilities. Talos does not reference CVE-2026-20131 in that report, and the indicators of compromise are different; the /var/tmp/license.tmp log entry that Cisco shared in July relates to CVE-2026-20079 and CVE-2026-20316, not this flaw. SecureLayer7 warns against treating those indicators as evidence of CVE-2026-20131 exploitation; Amazon's list remains the reference.

What defenders should check

Administrators should run the show version command on the FMC and use the Cisco Software Checker, which lists the first fixed release for each branch. Cisco issued hotfixes for branches 7.0, 7.2, 7.4, 7.6, 7.7, and 10.0 on July 29, with a broader hardening release promised for mid-September, so an FMC last updated in March is missing fixes for the other two flaws, even if protected from this one. Patching closes the hole but does not evict an intruder. If an FMC ran a vulnerable release between January 26 and the date it was patched, compare it against Amazon's indicators, which include the January exploit source 206.251.239.164 and the support domain cherryberry.click. Amazon notes file hashes are of little use because Interlock changes files for each victim.

Look for outbound HTTP PUT requests to outside hosts, web interface POST bodies starting with AC ED 00 05, unexpected HAProxy or fail2ban services on servers, cron entries that remove logs every five minutes, ScreenConnect software that was not installed by staff, and open TCP port 45588. Five-minute gaps in local logs are themselves a warning sign. Cisco's Snort rules 66082 and 66083 detect this exploit traffic. If any of these indicators appear, SecureLayer7 recommends rotating FMC credentials and the secrets used for managed devices, checking certificate enrollment in Active Directory, and contacting Cisco TAC. Cisco offers no workaround, though it notes that an FMC management interface without public internet access reduces the attack surface. SCC Firewall Management customers are already patched, and SecureLayer7 suggests reviewing administrative and configuration logs from January through March.

Sources: Cyber Kendra

Noor Haddad

Noor Haddad covers attacks, breach disclosures and exploited vulnerabilities for Five Nines. Noor writes from CISA and vendor advisories, SEC disclosures and published reporting.

Corrections. Report an error to corrections@thefivenines.com. We list substantive corrections on the corrections page.