CVE-2026-20316 remediation guide

Cisco Secure Firewall Management Center (FMC)

A vulnerability in the web interface of Cisco Secure Firewall Management Center (FMC) Software could allow an unauthenticated, remote attacker to log in to an affected device using a low-privileged account to access sensitive data within the impacted systems. This vulnerability is due to the presence of static user credentials for a low-privileged account. An attacker could exploit this vulnerability by using the account to log in to an affected system. A successful exploit could allow the attacker to log in to the affected system and access sensitive data as the low-privileged user.&n...

Open CVE record

Research in progress

A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.

ProductCisco Secure Firewall Management Center (FMC)

Affected versions>= 7.0.0, >= 7.0.0.1, >= 7.0.1, >= 7.0.1.1, >= 7.0.2, >= 7.2.0, >= 7.0.2.1, >= 7.0.3, >= 7.2.0.1, >= 7.0.4, >= 7.2.1, >= 7.0.5, >= 7.3.0, >= 7.2.2, >= 7.3.1, >= 7.2.3, >= 7.2.3.1, >= 7.2.4, >= 7.0.6, >= 7.2.4.1

Fixed versionsNo verified fixed-version field is available yet

Priority basisImmediate · CVSS 5.3 · EPSS 0.79%

Identify the affected asset

Confirm whether Cisco Secure Firewall Management Center (FMC) is installed, record the deployed version and installation path, and identify exposed interfaces.

Record the product name, package or appliance identifier, and installed version.
Identify internet-facing, administrative, API, and internal access paths.
Preserve the pre-change configuration and relevant service logs.

Validate the affected-version match

Compare the deployed version with the affected range: >= 7.0.0, >= 7.0.0.1, >= 7.0.1, >= 7.0.1.1, >= 7.0.2, >= 7.2.0, >= 7.0.2.1, >= 7.0.3, >= 7.2.0.1, >= 7.0.4, >= 7.2.1, >= 7.0.5, >= 7.3.0, >= 7.2.2, >= 7.3.1, >= 7.2.3, >= 7.2.3.1, >= 7.2.4, >= 7.0.6, >= 7.2.4.1. Treat incomplete inventory results as unresolved.

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

Apply supported remediation

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

Confirm the expected version and package state.
Run a functional health check for critical service paths.
Review authentication, error, application, and security monitoring logs.
Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.