Threat research Cisco firewall management

Cisco FMC under attack: protect the management plane

For an exposed firewall management console, the response needs an update and an investigation into whether it was accessed without authorization.

The management role changes the scope of the review

Cisco Secure Firewall Management Center, or FMC, centrally manages firewall policy and device configuration. An investigation should therefore follow its administrative reach, not stop at the console's operating system. Identify the firewalls it manages, the credentials it can access, and the teams responsible for the networks those firewalls protect.

Follow the management relationship

FMC management consolePolicy deployment, device configuration, and administrative access
Enterprise boundariesReview policy changes and administrative access.
Remote sitesInclude local owners and recovery arrangements.
Operational networksInclude OT owners where FMC manages the boundary.
Illustrative management scope, not an observed attack path. A console compromise warrants checking downstream configuration; it does not prove every managed firewall was compromised.

For a utility or industrial operator, the relevant question is whether this FMC controls a boundary the operational network depends on. If it does, review that policy with the OT network owner. Keep the management-console investigation and the safety of the operating environment in the same response plan.

Two exploited flaws. Different starting privileges.

CVE-2026-20079

Authentication bypass

10.0 CVSS v3.1 · Critical

Crafted HTTP requests can bypass authentication and obtain root access. Cisco identifies an improper process created at boot as the cause.

Cisco's authentication-bypass advisory

CVE-2026-20316

Static credentials

5.3 CVSS v3.1 · Cisco SIR High

A built-in low-privileged account permits access to sensitive data. Cisco rates the impact High because other vulnerabilities can enable privilege escalation.

Cisco's static-credential advisory

The lower score is not a reason to leave CVE-2026-20316 out of the change. CISA lists both vulnerabilities as exploited. Its current ransomware field is Unknown for CVE-2026-20079 and Known for CVE-2026-20316. The latter entered KEV on July 29 with an August 1 federal due date. CISA catalog data

What Talos observed, by intrusion cluster
ClusterReported entryObserved activity
UAT-12197CVE-2026-20079JSP web shell, JAR command execution, and credential theft.
UAT-11823CVE-2026-20079 or static credentialsReverse shell, managed-device configuration theft, and Cyclops Blink. Talos reports tooling overlap with Sandworm.
UAT-11988CVE-2026-20316Credential theft, SOCKS proxying, reverse SSH, and Qilin deployment on selected endpoints.

Cisco Talos, September 9. The ransomware cluster's documented entry was CVE-2026-20316.

Use the hotfix for the installed release

Match the device's actual software to Cisco's advisory before scheduling the change. A branch name alone does not establish that the required hotfix is installed. Confirm prerequisites, compatibility, and the resulting installation record with the team that owns FMC.

The same packages appear in both Cisco advisories, checked September 11
FMC releasePublished hotfix filename
7.0Cisco_Firepower_Mgmt_Center_Hotfix_GB-7.0.9.1-3.sh.REL.tar
7.2Cisco_Secure_FW_Mgmt_Center_Hotfix_HL-7.2.11.1-4.sh.REL.tar
7.4Cisco_Secure_FW_Mgmt_Center_Hotfix_HG-7.4.7.1-3.sh.REL.tar
7.6Cisco_Secure_FW_Mgmt_Center_Hotfix_CY-7.6.5.1-2.sh.REL.tar
7.7Cisco_Secure_FW_Mgmt_Center_Hotfix_AM-7.7.12.1-2.sh.REL.tar
10.0Cisco_Secure_FW_Mgmt_Center_Hotfix_P-10.0.1.1-2.sh.REL.tar

Confirm applicability and download through the CVE-2026-20079 advisory and the CVE-2026-20316 advisory.

Verify installation, not just the version number

Cisco says a hotfix does not change the displayed software version or build. Check successful installation in expert mode:

cat /etc/sf/patch_history

Cisco hotfix installation notes. Follow the notes for the installed release, including restrictions on configuration changes during installation.

Cloud-delivered management is a separate case. Cisco says the CVE-2026-20079 fix has already been deployed to Security Cloud Control Firewall Management, with no customer action required for that service. Do not treat this hotfix list as a firewall-device upgrade table.

Disclosure and remediation timeline
March 4
CVE-2026-20079 was publicly disclosed with software-update guidance. July was not its first disclosure or original fix date.
Late July
Further authentication-bypass hotfix and investigation guidance appeared. CVE-2026-20316 was disclosed on July 29.
September 9
Cisco acknowledged CVE-2026-20079 exploitation after learning of it in August. Talos published the intrusion analysis, and CISA added this CVE to KEV.

Sources: Cisco's March release, the two advisories, and CISA. Talos announced additional hardening for the following week; do not defer available fixes for that bundle.

Start with Cisco's log check, then follow the access

For authorized FMC administrators, Cisco provides this read-only search in expert mode, using the required privileges:

Cisco investigation check
zgrep "package_info.*license" /var/log/messages*

A result involving /var/tmp/license.tmp may indicate exploitation. Preserve relevant logs and contact Cisco TAC when compromise is suspected. Both advisories publish the check, so it is not a unique identifier for one CVE. Cisco's investigation and recovery guidance

  1. Contain exposure. Remove public management access and restrict internal access to approved administration paths. Confirm the effective access rules, including alternate management routes. This reduces reachability; it does not replace the patch.
  2. Give the investigation an owner. Review the exposure history, account activity, and changes around suspected access. The Talos report supplies cluster-specific indicators and detection references. A clean result from one search is not a complete review.
  3. Check management reach and egress together. Investigate unexplained outbound SSH and proxy connections against approved administration and backup jobs. Compare deployed firewall policy with a trusted baseline, not just the configuration currently on the manager.
  4. Plan recovery with the affected owners. Scope potentially exposed secrets and rotate or revoke them as part of a coordinated recovery. Confirm how administrators will regain trusted access before changing credentials across remote sites or operational boundaries.

The closing record should identify the installed hotfix, the configuration review outcome, and who made the recovery decision. That is more useful than an update timestamp on its own.

Sources and review scope

Reviewed September 11, 2026. Public exploitation claims come from Cisco and CISA. First-party figures come from a selected exact-match cohort in retained August archives, not a measurement of FMC exploitation or current fleet activity.