# CVE-2026-20079: Cisco Firewall Management Center Authentication Bypass Using an Alternate Path or Channel

> Unauthenticated remote attackers can bypass authentication and execute scripts to gain root access on Cisco Secure Firewall Management Center devices.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 9 Sep 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Mar 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-mv8w-c2qv-cgrg

## What is CVE-2026-20079?

CVE-2026-20079 is a critical authentication bypass vulnerability in Cisco Secure Firewall Management Center, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the web interface of Cisco Secure Firewall Management Center (FMC) Software could allow an unauthenticated, remote attacker to bypass authentication and execute script files on an affected device to obtain root access to the underlying operating system. 

This vulnerability is due to an improper system process that is created at boot time. An attacker could exploit this vulnerability by sending crafted HTTP requests to an affected device. A successful exploit could allow the attacker to execute a variety of scripts and commands that allow root access to the device. 

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2026-20079?

It affects 1 product.


Products: Cisco Secure Firewall Management Center.

## How do I fix CVE-2026-20079?

No fix has been published for CVE-2026-20079 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 12 Sep 2026.

## Is CVE-2026-20079 being exploited?

Yes. Attackers have exploited CVE-2026-20079 in the wild since at least 9 Sep 2026.

Public exploit code:

- Python proof of concept for CVE-2026-20079 affecting Cisco Secure Firewall Management Center. (github_poc): https://github.com/CyberAuth/CVE-2026-20079
- Cisco Secure Firewall Management Center Authentication Bypass RCE (metasploit)
- CVE-2026-20079 (github_poc): https://github.com/0xredash/CVE-2026-20079
- https://github.com/DiegoArias008/CVE-2026-20079-checker (github_poc): https://github.com/DiegoArias008/CVE-2026-20079-checker
- Cisco Secure Firewall Management Center - Authentication Bypass (nuclei): http/cves/2026/CVE-2026-20079.yaml

## Other vulnerabilities in Cisco Secure Firewall Management Center

- [CVE-2026-20131](https://insights.sbomify.com/CVE-2026-20131/): Cisco Secure Firewall Management Center (FMC) Software and Cisco Security Cloud Control (SCC) Firewall Management Deserialization of Untrusted Data (critical 10.0, exploited in the wild)
- [CVE-2026-20316](https://insights.sbomify.com/CVE-2026-20316/): Cisco Secure Firewall Management Center Use of Hard-coded Password (medium 5.3, exploited in the wild)
- [CVE-2025-20265](https://insights.sbomify.com/CVE-2025-20265/): Cisco Secure Firewall Management Center Software Radius Remote Code Execution Vulnerability (critical 10.0)
- [CVE-2024-20424](https://insights.sbomify.com/CVE-2024-20424/): Command injection in Cisco Firepower Management Center (critical 9.9)
- [CVE-2023-20048](https://insights.sbomify.com/CVE-2023-20048/): Missing authorization in Cisco Firepower Management Center (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-20079 and fix it if it is affected.

What it is: CVE-2026-20079 is a critical authentication bypass vulnerability in Cisco Secure Firewall Management Center, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-20079 in the wild since at least 9 Sep 2026.

Affected product: Cisco Secure Firewall Management Center. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-20079/ (Markdown: https://insights.sbomify.com/CVE-2026-20079/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-20079
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-20079
- OSV: https://osv.dev/vulnerability/CVE-2026-20079

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-20079/
Summaries are generated and may contain mistakes; the official description above is the record.