Exploited vulnerability

Cisco Secure Firewall Management Center Authentication Bypass (CVE-2026-20079)

A critical authentication bypass in the web interface of Cisco Secure Firewall Management Center (FMC).

  • On CISA KEV
CVE ID
CVE-2026-20079
CVSS
10.0 Critical (CVSS v3.1, Cisco as CNA; no CVSS 4.0 score in the record or NVD)
CISA KEV
Listed
Affected product
Cisco Secure Firewall Management Center (FMC) Software; Cisco Security Cloud Control (SCC) Firewall Management
Exploited
Yes
Published
4 March 2026 (Cisco advisory and CVE record); in CISA KEV 9 September 2026

In short

CVE-2026-20079 is a critical authentication bypass in the web interface of Cisco Secure Firewall Management Center (FMC). An unauthenticated remote attacker can send crafted HTTP requests, run scripts and obtain root access. Cisco rates it CVSS 3.1 10.0, and CISA added it to the KEV catalog on 9 September 2026.

Profile MapVulnerability
  1. CVECVE-2026-20079
  2. ProductCisco Cisco Secure Firewall Management Center (FMC) Software; Cisco Security Cloud Control (SCC) Firewall Management
  3. CISA KEVListedKnown Exploited Vulnerabilities
  4. ExploitedYesin real attacks
  5. Fix Steps5actions listedCheck the Messages Logs

What it allows

Cisco says a flaw in the web interface of Cisco Secure Firewall Management Center (FMC) Software lets an unauthenticated, remote attacker bypass authentication and execute script files on the device. The attacker obtains root access to the underlying operating system. Cisco rates it CVSS 3.1 10.0 Critical.

FMC is the management console for Cisco Secure Firewall devices. Cisco says the flaw affects FMC Software and Cisco Security Cloud Control (SCC) Firewall Management regardless of device configuration. SCC Firewall Management is a SaaS offering, and Cisco says it has already deployed the fix there.

Why a Boot-Time Process Opens the Door

Cisco attributes the flaw to an improper system process that is created at boot time. An attacker sends crafted HTTP requests to the device, and a successful exploit can run scripts and commands that give root access. Cisco notes that the attack surface is smaller when the FMC management interface has no public internet access.

VulnCheck built a working exploit and published its analysis on 26 March 2026. It says the startup process leaves a partial session in the FMC database. If nobody authenticates after boot, that session persists, and an attacker can upgrade it into one with usable permissions.

VulnCheck also says the bypass has prerequisites. The host must have rebooted, and normal activity such as user logins or dashboard use can clear the session. It concludes that a target is likely exploitable only shortly after boot, or on systems that rarely see web interface activity.

Do not read those prerequisites as a safe state. Cisco lists the flaw as affecting FMC regardless of configuration, and both Cisco and CISA report exploitation. VulnCheck cites about 300 FMC instances on the public internet in Censys and 600 to 700 in FOFA.

Exploitation Signals for CVE-2026-20079

These are the public signals we checked on 4 November 2026. Each row names who says it.

Exploit signals
  • CISA KEVYesAdded 9 September 2026 with a due date of 12 September 2026; ransomware use listed as Unknown, forensic triage listed as Yes4 Nov
  • Cisco PSIRTYesSays it became aware of active exploitation in August 20264 Nov
  • Exploitation in CISA SSVC (via NVD)YesExploitation active, automatable yes, technical impact total, dated 10 September 20264 Nov
  • Public code on GitHubYesThree repositories named for the CVE, created on 28 March, 17 August and 13 September 20264 Nov
  • Brandefense BlackholeYes29 retrieved posts name the CVE id between 5 June and 15 September 2026; 26 are dated 9 to 15 September4 Nov
Verdict Exploited per Cisco; in CISA KEV since 9 September 2026

The README of the earliest repository, created on 28 March, is an overview of the flaw. The second, created on 17 August, says it holds a Python proof of concept that implements the request sequence VulnCheck published. The third says it is a read-only checker without the exploit steps. We do not link them.

On 20 August 2026 a researcher posted to the Full Disclosure mailing list that the public chain was independently reproduced on FMC 10.0.1-1 with confirmed root execution. The post says the work does not claim discovery of the flaw. It points to a write-up dated 15 August by Arian Eidizadeh.

Most Blackhole posts are Telegram and forum items from 9 to 15 September that repeat news of the CISA listing and Cisco's confirmation.

How to Check for Signs of Exploitation

Cisco gives one check. In expert mode, run zgrep "package_info.*license" on the messages logs. If the output includes /var/tmp/license.tmp, Cisco says the device may have been exploited.

Cisco says its hot fixes are for preventing future exploitation and may not address an existing compromise. If you suspect exploitation, contact Cisco TAC for recovery options. Cisco says Brandon Sakai of Cisco found the flaw during internal security testing.

Cisco's firewall line has had other recent flaws, such as the Cisco ASA and FTD flaw CVE-2026-76418. Our Cisco vulnerability tracker lists more Cisco advisories.

Who is affected

Cisco says the flaw affects Secure Firewall Management Center Software and Cisco Security Cloud Control (SCC) Firewall Management, regardless of configuration. NVD lists FMC releases from 7.0.0 up to 10.0.1, including 7.1 and 7.3 releases that have no row of their own in Cisco's table. The table below follows Cisco's fixed-release table row by row.

FMC releaseReleases before the fixFirst fixed release
7.0 and earlierAffectedFixed7.0.10
7.2AffectedFixed7.2.12
7.4AffectedFixed7.4.8
7.6AffectedFixed7.6.6
7.7AffectedFixed7.7.13
10.0AffectedFixed10.0.2
10.1AffectedFixed10.1.0
  • Affected
  • Fixed

Cisco says it first provided hot fixes. It has since published hardening releases that include this fix and several other internally found fixes, and it recommends upgrading to the matching hardening release. Customers who need details on the old hot fixes should contact Cisco TAC.

Cisco confirms that these products are not affected: Firewall Device Manager (FDM), Secure Firewall ASA Software, Secure Firewall Threat Defense (FTD) Software and Security Cloud Control (SCC), formerly Defense Orchestrator. Cisco lists no workaround. Its Software Checker tool shows which advisories apply to a given release.

Cisco published the advisory on 4 March 2026 in its March 2026 bundled publication for Secure Firewall ASA, FMC and FTD. It last updated the advisory on 16 September 2026. Our vulnerability management guide covers how to plan and check a rollout.

Timeline

  1. 4 Mar 2026

    Cisco publishes the advisory and the CVE record goes public.

  2. 26 Mar 2026

    VulnCheck publishes its analysis of the authentication bypass and root code execution chain.

  3. 28 Mar 2026

    The earliest GitHub repository named for the CVE is created.

  4. Aug 2026

    Cisco says its PSIRT became aware of active exploitation.

  5. 17 Aug 2026

    A GitHub repository that says it holds a Python proof of concept is created.

  6. 20 Aug 2026

    A researcher posts to the Full Disclosure mailing list that the public chain was independently reproduced on FMC 10.0.1-1.

  7. 9 Sep 2026

    CISA adds the CVE to KEV with a due date of 12 September 2026.

  8. 16 Sep 2026

    Cisco publishes version 2.6 of the advisory, which lists the hardening releases.

What to do

  1. Upgrade FMC to the First Fixed Release

    Move FMC to 7.0.10, 7.2.12, 7.4.8, 7.6.6, 7.7.13, 10.0.2 or 10.1.0, whichever matches your train. Cisco lists no workaround.

  2. Check the Messages Logs

    In expert mode, run zgrep "package_info.*license" on the messages logs. Cisco says a hit that includes /var/tmp/license.tmp means the device may have been exploited.

  3. Contact Cisco TAC if You Suspect Exploitation

    Cisco says its hot fixes are for preventing future exploitation and may not address an existing compromise. Follow TAC guidance on recovery.

  4. Keep the FMC Interface Off the Internet

    Cisco says the attack surface is smaller when the management interface has no public internet access. We recommend allowing the interface only from trusted admin networks.

  5. Confirm SCC Firewall Management Status

    Cisco says it already deployed the fix to SCC Firewall Management environments and that no user action is required there.

Questions

Is CVE-2026-20079 exploited?

Cisco says its PSIRT became aware of active exploitation in August 2026. CISA added the CVE to KEV on 9 September 2026 with a due date of 12 September 2026.

Are Firepower Threat Defense and ASA devices affected?

No. Cisco confirms that FTD Software, ASA Software, Firewall Device Manager and Security Cloud Control (formerly Defense Orchestrator) are not affected. The flaw is in FMC and in the separate SCC Firewall Management service.

Is there a workaround for CVE-2026-20079?

Cisco says no workaround addresses the flaw. It notes that the attack surface is smaller when the FMC management interface has no public internet access.

How do I check whether my FMC was exploited?

Cisco says to run zgrep "package_info.*license" on the messages logs in expert mode. A hit that includes /var/tmp/license.tmp means the device may have been exploited.

Does the cloud service need patching?

Cisco says the fix is already deployed to Cisco Security Cloud Control Firewall Management environments and that no user action is required there.

Sources

  1. Cisco Secure Firewall Management Center Software Authentication Bypass Vulnerability (cisco-sa-onprem-fmc-authbypass-5JPp45V2) Cisco
  2. CVE-2026-20079 Record CVE Program / Cisco CNA
  3. CVE-2026-20079 NVD
  4. Known Exploited Vulnerabilities Catalog CISA
  5. CVE-2026-20079 - Cisco FMC Authentication Bypass RCE Analysis VulnCheck
  6. CVE-2026-20079 - Cisco Secure Firewall Management Center Authentication Bypass to Root RCE Full Disclosure mailing list