Advisory

CVE-2026-20079 (CVSS 10): Cisco FMC Authentication Bypass Grants Remote Root Access

A critical authentication-bypass flaw in Cisco Secure Firewall Management Center (FMC) and Security Cloud Control (SCC) Firewall Management allows an unauthenticated remote attacker to execute scripts and obtain root access to the underlying operating system. The vulnerability carries the maximum possible CVSS score of 10.0 and has been added to the CISA Known Exploited Vulnerabilities (KEV) catalog.

TL;DR: Apply Cisco's patches immediately in accordance with vendor instructions and CISA BOD 26-04 guidance. If mitigations are unavailable, CISA directs affected organizations to discontinue use of the product.

What Is the Flaw?

CVE-2026-20079 is an authentication bypass using an alternate path or channel (CWE-288) in the web interface of Cisco Secure Firewall Management Center (FMC) Software. The vulnerability was published to the NVD on 4 March 2026.

According to the NVD description, the root cause is an improper system process that is created at boot time. This design defect creates an alternate channel into the web interface that exists outside the normal authentication flow, meaning an attacker never needs valid credentials to reach it.

An attacker exploits the flaw by sending crafted HTTP requests to the affected device over the network. A successful exploit allows the attacker to execute a variety of scripts and commands, ultimately yielding root access to the underlying operating system. No user interaction is required, and no prior privileges are needed.

The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H reflects all of these characteristics and results in the maximum possible base score of 10.0 (Critical). The scope is marked Changed (S:C), indicating the impact extends beyond the vulnerable component itself to the broader operating environment.

Who and What Is Affected?

The vulnerability affects the web interface of:

  • Cisco Secure Firewall Management Center (FMC) Software
  • Cisco Security Cloud Control (SCC) Firewall Management

Cisco's own advisory and the CISA KEV entry are the authoritative sources for the specific software versions that are vulnerable and those that contain fixes. Organizations should consult the Cisco Security Advisory directly to determine whether their deployed versions are in scope.

Because FMC and SCC are centralized management planes for firewall policy across an enterprise, a compromise of these systems has potential consequences far beyond the management appliance itself — an attacker with root on FMC could have visibility into, and potentially influence over, the firewall rules governing an entire network.

What Is the Impact?

The impact of a successful exploit is severe across all three security dimensions:

  • Confidentiality (High): An attacker with root access can read all data on the system, including stored credentials, configuration secrets, and information about managed firewall policies.
  • Integrity (High): Root-level script execution allows an attacker to modify system files, alter firewall rules pushed to managed devices, or plant persistent backdoors.
  • Availability (High): The attacker can disrupt or disable the management platform, preventing legitimate administrators from managing connected firewall infrastructure.

The Changed scope indicator in the CVSS vector is particularly significant here. Because FMC is a management plane for other network security devices, an attacker who obtains root on FMC can potentially pivot to influence the security posture of every firewall it manages — multiplying the blast radius well beyond the initial target.

CISA added this vulnerability to the Known Exploited Vulnerabilities (KEV) catalog on 9 September 2026, confirming that exploitation has been observed in real-world environments. Federal civilian executive branch (FCEB) agencies are bound by BOD 26-04 remediation timelines; all organizations should treat this with equivalent urgency.

What Should You Do Now?

CISA's KEV required action specifies the following steps. Organizations should act immediately:

  1. Apply vendor mitigations. Consult the official Cisco Security Advisory for CVE-2026-20079 and apply patches or mitigations in accordance with Cisco's instructions.
  2. Follow BOD 26-04 guidance. CISA's Binding Operational Directive 26-04 sets prioritized patching timelines based on asset risk. All organizations — not just federal agencies — should use this framework as a minimum baseline.
  3. Complete forensic triage. CISA's KEV entry references specific Forensics Triage Requirements. Given that exploitation has been confirmed, organizations should evaluate whether affected systems may have already been compromised before patching was applied.
  4. Restrict network access to management interfaces. If patching cannot be completed immediately, limit access to the FMC and SCC web interface at the network layer. Management planes should never be exposed directly to the internet.
  5. Discontinue use if mitigations are unavailable. Per CISA's required action, if no mitigations are available for a given deployment (including cloud service variants), organizations should discontinue use of the product until a fix is available and applied.

Primary references:

How External Testing Surfaces This Exposure

An unauthenticated, network-exploitable vulnerability in a management interface is precisely the kind of risk that point-in-time external vulnerability assessments are designed to detect. A well-scoped external assessment can identify:

  • Exposed management interfaces. FMC and SCC web interfaces that are reachable from the internet or from untrusted network segments represent an immediate, critical exposure. External scanning reveals whether these ports and services are accessible before an attacker discovers them.
  • Unpatched software versions. Version detection during an assessment can flag whether deployed FMC instances fall within the vulnerable version range identified by Cisco, prioritizing remediation effort.
  • Network segmentation gaps. Assessments that map the attack surface can confirm whether management-plane services are appropriately isolated — or whether a lateral path exists from less-trusted zones to the FMC web interface.

Because this vulnerability requires only network access and crafted HTTP requests — no credentials, no user interaction — the attack surface is entirely determined by where the management interface is reachable. Reducing and validating that exposure is a concrete, actionable step organizations can take alongside patching.

Sources & further reading: NVD CVE-2026-20079 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: sec.cloudapps.cisco.com, seclists.org, blog.talosintelligence.com, cisa.gov. This advisory contains no exploit code.

Frequently asked questions

Does an attacker need any credentials or insider access to exploit CVE-2026-20079?

No. The CVSS vector confirms that no privileges (PR:N) and no user interaction (UI:N) are required. An unauthenticated remote attacker can send crafted HTTP requests directly to the affected web interface and exploit the flaw without any prior foothold.

Is this vulnerability being actively exploited?

Yes. CISA added CVE-2026-20079 to the Known Exploited Vulnerabilities (KEV) catalog on 9 September 2026, which means exploitation has been observed in real-world environments. This makes prompt patching and forensic triage especially important.

My FMC is not directly internet-exposed — am I safe?

Network isolation significantly reduces risk, but it does not eliminate it. The vulnerability is exploitable by any attacker who can reach the FMC web interface over the network, including from internal segments or via a compromised host inside the perimeter. Organizations should validate segmentation controls and apply Cisco's patches regardless of perceived exposure level.

Where can I find the official list of affected and fixed software versions?

The definitive version information is in Cisco's official Security Advisory for CVE-2026-20079, available through Cisco's Security Advisory portal at sec.cloudapps.cisco.com. The NVD entry at nvd.nist.gov/vuln/detail/CVE-2026-20079 also links to vendor references. Always consult the vendor advisory directly, as version scope may be updated as Cisco's investigation continues.