# CVE-2026-20316: Cisco Secure Firewall Management Center Use of Hard-coded Password

> An unauthenticated attacker can log in using static low-privileged credentials to access sensitive data in Cisco Secure Firewall Management Center.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Yes, since 29 Jul 2026 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-x85f-hvgg-4944

## What is CVE-2026-20316?

CVE-2026-20316 is a medium-severity vulnerability in Cisco Secure Firewall Management Center, published on 29 Jul 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 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.

Weakness: CWE-259 (Use of Hard-coded Password)

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

It affects 1 product.


Products: Cisco Secure Firewall Management Center.

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

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

## Is CVE-2026-20316 being exploited?

Yes. Attackers have exploited CVE-2026-20316 in the wild since at least 29 Jul 2026, including in ransomware campaigns.

## Other vulnerabilities in Cisco Secure Firewall Management Center

- [CVE-2026-20079](https://insights.sbomify.com/CVE-2026-20079/): Cisco Firewall Management Center Authentication Bypass Using an Alternate Path or Channel (critical 10.0, exploited in the wild)
- [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-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-20316 and fix it if it is affected.

What it is: CVE-2026-20316 is a medium-severity vulnerability in Cisco Secure Firewall Management Center, published on 29 Jul 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-20316 in the wild since at least 29 Jul 2026, including in ransomware campaigns.

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-20316/ (Markdown: https://insights.sbomify.com/CVE-2026-20316/index.md)
```

## Sources

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

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