Cisco Secure Firewall Management Center static-credential flaw CVE-2026-20316 exploited as zero-day

Cisco has confirmed in-the-wild exploitation of CVE-2026-20316, a static-credential vulnerability in the web interface of Cisco Secure Firewall Management Center (FMC). The flaw lets a remote, unauthenticated attacker log in with a built-in low-privileged account and read sensitive data. CISA added it to the Known Exploited Vulnerabilities catalogue and gave federal civilian agencies until 1 August 2026 to remediate.

Technical details

  • The root cause is a hard-coded password for a built-in account (CWE-259). The flaw was discovered by Jimi Sebree of Horizon3.ai.
  • Cisco raised its own Security Impact Rating to High, because the low-privileged access can be chained with other FMC bugs to escalate privileges.
  • Affected on-premises FMC releases span 7.0 through 10.0. Cloud-delivered FMC, Firewall Device Manager, ASA, FTD and Security Cloud Control are not affected.
  • Cisco has not said when the attacks began or who is behind them. Its advisory also covers CVE-2026-20079, a CVSS 10.0 authentication bypass in FMC that allows script execution as root. Both bugs share the same indicator of compromise, which suggests they can be chained.

Fixed versions

Cisco released hotfixes for each supported branch: 7.0.9.1, 7.2.11.1, 7.4.7.1, 7.6.5.1, 7.7.12.1 and 10.0.1.1. Horizon3 states that no workaround exists.

Impact

FMC centrally manages Cisco firewall policy, so compromise of the management plane gives an attacker insight into, and potentially control over, an organisation’s perimeter defences. Risk is much lower where the FMC management interface is not reachable from the internet.

Recommendations

  • Install the Cisco hotfix for your FMC branch immediately.
  • Hunt for exploitation: in expert mode, run zgrep "package_info.*license" messages* in the log directory and look for references to /var/tmp/license.tmp.
  • If the indicator is present, open a case with Cisco TAC and rotate all credentials, keys and certificates stored on the appliance.
  • Remove any public exposure of the FMC management interface and restrict it to a dedicated management network.

Sources