CVE-2026-20131 remediation guide

Cisco Secure Firewall Management Center (FMC)

A vulnerability in the web-based management interface of Cisco Secure Firewall Management Center (FMC) Software could allow an unauthenticated, remote attacker to execute arbitrary Java code as root on an affected device. This vulnerability is due to insecure deserialization of a user-supplied Java byte stream. An attacker could exploit this vulnerability by sending a crafted serialized Java object to the web-based management interface of an affected device. A successful exploit could allow the attacker to execute arbitrary code on the device and elevate privileges to root. Note: If th...

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 versions7.0.0, 7.0.0.1, 7.0.1, 7.1.0, 6.4.0.13, 7.0.1.1, 6.4.0.14, 7.1.0.1, 7.0.2, 6.4.0.15, 7.2.0, 7.0.2.1, 7.0.3, 7.1.0.2, 7.2.0.1, 7.0.4, 7.2.1, 7.0.5, 6.4.0.16, 7.3.0

Fixed versionsNo verified fixed-version field is available yet

Priority basisImmediate · CVSS 10 · EPSS 28.2%

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.1.0, 6.4.0.13, 7.0.1.1, 6.4.0.14, 7.1.0.1, 7.0.2, 6.4.0.15, 7.2.0, 7.0.2.1, 7.0.3, 7.1.0.2, 7.2.0.1, 7.0.4, 7.2.1, 7.0.5, 6.4.0.16, 7.3.0. 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 per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

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.