Security tracker
CVE-2026-20316: Cisco Secure Firewall Management Center Use of Hard-coded Password Vulnerability
In short
Cisco Secure Firewall Management Center (FMC) has a weakness classified as use of hard-coded password (CWE-259). CISA added it to its Known Exploited Vulnerabilities catalog on 2026-07-29. NVD lists CVSS 3.1 at 5.3 MEDIUM. CISA reports known ransomware campaign use.
What it is
“Cisco Secure Firewall Management Center (FMC) formerly known as Firepower Management Center contains a use of hard-coded password vulnerability that 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.” — CISA KEV, retrieved 2026-11-01
“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. Note: If the FMC management interface does not have public internet access, the attack surface that is associated with this vulnerability is reduced. Cisco has assigned this security advisory a Security Impact Rating (SIR) of High rather than Medium as the score indicates. The reason is that this vulnerability can be used with other Cisco Secure FMC Software vulnerabilities to elevate privileges.” — NVD, retrieved 2026-11-01
Who is affected
Cisco Secure Firewall Management Center (FMC). NVD lists the following versions as affected:
- Versions from 7.0.0 inclusive, through 7.0.9
- Versions from 7.2.0 inclusive, through 7.2.11
- Versions from 7.3.0 inclusive, through 7.3.1.2
- Versions from 7.4.0 inclusive, through 7.4.7
- Versions from 7.6.0 inclusive, through 7.6.5
- Versions from 7.7.0 inclusive, through 7.7.12
- Versions from 10.0.0 inclusive, through 10.0.1
Exploitation status
CISA KEV added: 2026-07-29. Known ransomware campaign use: Known (reported by CISA). Due date CISA set for US federal civilian agencies: 2026-08-01.
Scores
NVD CVSS 3.1: 5.3 MEDIUM; vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N; source [email protected].
EPSS by FIRST: 35.10%; percentile 98.44; score date 2026-10-31. EPSS estimates the probability of exploitation in the next 30 days.
CWE: CWE-259.
Timeline
| Date | Event |
|---|---|
| 2026-07-29 | CISA KEV added |
| 2026-07-29T17:16:51.840 | NVD published |
| 2026-08-01 | CISA KEV due |
| 2026-10-24T13:10:00.147 | NVD last modified |
| 2026-10-31 | FIRST EPSS score |
CISA required action
“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.” — CISA KEV
What to do
- Confirm whether you run Cisco Secure Firewall Management Center (FMC) and which version.
- Apply the vendor update or mitigation in the advisory.
- Follow CISA’s required action.
- Review the vendor guidance on signs of compromise.
- Track the fix through completion.
Sources and dates
CISA Known Exploited Vulnerabilities Catalog, version 2026.10.30; retrieved 2026-11-01. CISA KEV data: CC0 1.0. No endorsement by CISA.
NVD retrieved: 2026-11-01. This product uses the NVD API but is not endorsed or certified by the NVD.
EPSS scores by FIRST; score date 2026-10-31.
Check your own domain's public security settings
The snapshot checks a domain you own or are authorized to check for DNS, HTTPS/TLS and web-header hygiene. It does not test for this CVE.