NETWORK INCIDENTS

Exploited now

Remediation guide
Cisco · Secure Firewall Management Center (FMC) and Security Cloud Control (SCC) Firewall Management

CVE-2026-20079

Cisco Secure Firewall Management Center Software Authentication Bypass Vulnerability

CISA KEV
Known exploitedadded 9 Sep 2026; US federal deadline 12 Sep 2026
Exploit likelihood
89%100th percentile · FIRST EPSS, 2026-11-15
Severity
10.0 CriticalCVSS 3.1, Cisco
Last verified
30 Oct 2026against the sources below

1In plain language

A flaw in the web interface of Cisco Secure Firewall Management Center (FMC) Software could let a remote attacker who hasn't logged in bypass authentication and run script files on the device, getting root access to its operating system.

If the FMC management interface has no public internet access, the attack surface is reduced.

Cisco became aware of active exploitation in August 2026, and CISA lists it as known to be exploited.

2Am I affected?

It affects Cisco Secure FMC Software and Cisco Security Cloud Control (SCC) Firewall Management, regardless of device configuration.

SCC Firewall Management is SaaS and upgraded by Cisco: the fix has been deployed there, and no user action is required.

Cisco has confirmed it does not affect Firewall Device Manager (FDM), Secure Firewall ASA Software, Secure Firewall Threat Defense (FTD) Software, or Security Cloud Control (SCC), formerly Defense Orchestrator. (That's not the same as SCC Firewall Management above, which is affected and already fixed by Cisco.)

Cisco's record also lists FMC 7.1 and 7.3 as affected, but Cisco's fix table leaves them out: see Fix. our analysis

Affected releases are summarised by release train in the Fix table.

Check your version

A command to show the running FMC release: Not stated by vendor.

Cisco provides the Cisco Software Checker to find the advisories that affect a specific software release, and the earliest release that fixes them. Source ↗

3Fix

Cisco's table heading names both FTD and FMC releases, but FTD isn't affected by this CVE (above): for this vulnerability the table is about FMC. our analysis

The fixed releases are hardening releases that include this fix along with other internally discovered vulnerabilities, and Cisco recommends upgrading to the appropriate one. Earlier hot fixes for this CVE are for preventing future exploitation only and may not address existing compromise.

If you applied one of the earlier hot fixes, Cisco says to contact TAC for more information on them.

Cisco's record also lists FMC 7.1 (7.1.0 to 7.1.0.3) and 7.3 (7.3.0 to 7.3.1.2) as affected, and the fix table has no row for either train: Cisco lists no fixed release in them.

If you run 7.1 or 7.3, use the Cisco Software Checker or ask Cisco TAC which release to move to. our analysis

Cisco says the earlier hot fixes may not address an existing compromise, and doesn't say the hardening releases do. Don't treat an upgrade as a clean-up: run the check under Was I hit? before you upgrade, and contact TAC if it matches. our analysis

ProductReleaseFirst fixed release
Cisco Secure FTD Software and Secure FMC Software7.0 and earlier7.0.10
7.1Not stated by vendor: affected per the vendor's record; this train is not in the vendor's fix table
7.27.2.12
7.3Not stated by vendor: affected per the vendor's record; this train is not in the vendor's fix table
7.47.4.8
7.67.6.6
7.77.7.13
10.010.0.2
10.110.1.0

4Can't patch tonight?

There are no workarounds that address this vulnerability.

Keeping the FMC management interface off the public internet reduces the attack surface, but it isn't a workaround.

5Was I hit?

To check whether it may have been exploited, Cisco says to run this command in expert mode (Cisco's example runs it as root). If a log message in the output includes /var/tmp/license.tmp, the vulnerability may have been exploited on the device.

> zgrep "package_info.*license" /var/log/messages*

In the output, look at the /var/tmp/license.tmp line.

CISA's catalog flags this CVE for forensic triage, and its required action points to CISA's BOD 26-04 guidance and its Forensics Triage Requirements. Source ↗

If exploitation is suspected, contact Cisco TAC immediately for recovery options, and follow all TAC guidance if indicators of compromise are present.

6Sources

Summary of public vendor guidance. Verify against the vendor advisory before acting.

See CVE-2026-20079 in the exploited-now list (exploit likelihood, CISA's description, deadline).

More Cisco guides