cve.bz

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

10.0 criticalKEVExploitEPSS 89%

Critical (10.0) in Cisco Secure Firewall Management Center (FMC) and Security Cloud Control (SCC) Firewall Management. In CISA KEV since 2026-09-09. EPSS 89% estimated probability of exploitation activity in the next 30 days.

On this page
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. 

Severity

CVSS 3.1

10.0 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
89% (unchanged from 89% a week ago; 88% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-09-09, due 2026-09-12
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: total, assessed 2026-09-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-288 Authentication Bypass Using an Alternate Path or Channel
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-20079 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-20079?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-20079?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-20079 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
cisco:secure_firewall_management_center7.0.0
cisco:secure_firewall_management_center7.0.0.1
cisco:secure_firewall_management_center7.0.1
cisco:secure_firewall_management_center7.0.1.1
cisco:secure_firewall_management_center7.0.2
cisco:secure_firewall_management_center7.0.2.1
cisco:secure_firewall_management_center7.0.3
cisco:secure_firewall_management_center7.0.4
cisco:secure_firewall_management_center7.0.5
cisco:secure_firewall_management_center7.0.6
cisco:secure_firewall_management_center7.0.6.1
cisco:secure_firewall_management_center7.0.6.2
cisco:secure_firewall_management_center7.0.6.3
cisco:secure_firewall_management_center7.0.7
cisco:secure_firewall_management_center7.0.8
cisco:secure_firewall_management_center7.0.8.1
cisco:secure_firewall_management_center7.0.9
cisco:secure_firewall_management_center7.1.0
cisco:secure_firewall_management_center7.1.0.1
cisco:secure_firewall_management_center7.1.0.2
cisco:secure_firewall_management_center7.1.0.3
cisco:secure_firewall_management_center7.2.0
cisco:secure_firewall_management_center7.2.0.1
cisco:secure_firewall_management_center7.2.1
cisco:secure_firewall_management_center7.2.2
cisco:secure_firewall_management_center7.2.3
cisco:secure_firewall_management_center7.2.3.1
cisco:secure_firewall_management_center7.2.4
cisco:secure_firewall_management_center7.2.4.1
cisco:secure_firewall_management_center7.2.5
cisco:secure_firewall_management_center7.2.5.1
cisco:secure_firewall_management_center7.2.5.2
cisco:secure_firewall_management_center7.2.6
cisco:secure_firewall_management_center7.2.7
cisco:secure_firewall_management_center7.2.8
cisco:secure_firewall_management_center7.2.8.1
cisco:secure_firewall_management_center7.2.9
cisco:secure_firewall_management_center7.2.10
cisco:secure_firewall_management_center7.2.10.1
cisco:secure_firewall_management_center7.2.10.2
cisco:secure_firewall_management_center7.2.11
cisco:secure_firewall_management_center7.3.0
cisco:secure_firewall_management_center7.3.1
cisco:secure_firewall_management_center7.3.1.1
cisco:secure_firewall_management_center7.3.1.2
cisco:secure_firewall_management_center7.4.0
cisco:secure_firewall_management_center7.4.1
cisco:secure_firewall_management_center7.4.1.1
cisco:secure_firewall_management_center7.4.2
cisco:secure_firewall_management_center7.4.2.1
cisco:secure_firewall_management_center7.4.2.2
cisco:secure_firewall_management_center7.4.2.3
cisco:secure_firewall_management_center7.4.2.4
cisco:secure_firewall_management_center7.4.3
cisco:secure_firewall_management_center7.4.4
cisco:secure_firewall_management_center7.4.5
cisco:secure_firewall_management_center7.4.6
cisco:secure_firewall_management_center7.4.7
cisco:secure_firewall_management_center7.6.0
cisco:secure_firewall_management_center7.6.1
cisco:secure_firewall_management_center7.6.2
cisco:secure_firewall_management_center7.6.2.1
cisco:secure_firewall_management_center7.6.3
cisco:secure_firewall_management_center7.6.4
cisco:secure_firewall_management_center7.6.5
cisco:secure_firewall_management_center7.7.0
cisco:secure_firewall_management_center7.7.10
cisco:secure_firewall_management_center7.7.10.1
cisco:secure_firewall_management_center7.7.11
cisco:secure_firewall_management_center7.7.12
cisco:secure_firewall_management_center10.0.0
cisco:secure_firewall_management_center10.0.1

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-127 Directory Indexing Likelihood: High · Severity: Medium
  • CAPEC-665 Exploitation of Thunderbolt Protection Flaws Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON