CVE-2026-20079: Cisco FMC unauthenticated authentication bypass to root

Quick Answer

CISA added CVE-2026-20079 to its Known Exploited Vulnerabilities catalog on 2026-09-09, confirming that exploitation has occurred. If you operate Cisco Secure Firewall Management Center (FMC) and Security Cloud Control (SCC) Firewall Management, identify the exact version and relevant configuration now, preserve security evidence, and follow the live vendor remediation. A KEV match does not prove your system was compromised, and installing an update does not rule out earlier exploitation.

Last verified: 2026-09-17 UTC. CISA KEV snapshot version 2026.09.16. Recheck the live advisory before changing production.

Context

Status At A Glance

Product scope	Cisco — Secure Firewall Management Center (FMC) and Security Cloud Control (SCC) Firewall Management
CVE	CVE-2026-20079
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-09-09
Vendor severity	Critical
CVSS	CVSS 3.1 base 10.0 — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Ransomware field	Unknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage field	Yes — CISA's record calls for forensic triage.
CWE	CWE-288
Federal remediation date	2026-09-12 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Cisco Firewall Management Center Authentication Bypass Using an Alternate Path or Channel Vulnerability. Cisco Secure Firewall Management Center (FMC) Software and Cisco Security Cloud Control (SCC) Firewall Management contain an authentication Bypass using an alternate path or channel vulnerability that 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. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Cisco Secure Firewall Management Center (FMC) Software and Cisco Security Cloud Control (SCC) Firewall Management contain an authentication Bypass using an alternate path or channel vulnerability that 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.

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

1. Confirm. Inventory every Secure Firewall Management Center (FMC) and Security Cloud Control (SCC) Firewall Management asset and record its exact version, patch level, role, relevant configuration, and exposure.
2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Cisco advisory.
4. Remediate. Remove public access to the FMC management interface where possible, preserve evidence, run Cisco's documented indicator check, and upgrade to the fixed hardening release for the installed train. Contact Cisco TAC immediately if exploitation is suspected.
5. Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Investigation And Recovery

Cisco documents a zgrep check for package_info/license activity and warns hot fixes prevent future exploitation but may not address existing compromise. Contact Cisco TAC if indicators are present. CISA marks forensic triage Yes.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: In August 2026, Cisco PSIRT became aware of active exploitation.

CISA statement: CVE-2026-20079 was added to KEV on 2026-09-09. The ransomware field is Unknown, and the forensic-triage field is Yes. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

• TechGeeks Security Notice Center
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Cisco advisory or support notice
• CISA guidance
• CISA guidance
• NVD CVE record
• CISA source

Wrap-Up

Record whether CVE-2026-20079 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.