⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Critical · CVSS 10 ⚠ ACTIVELY EXPLOITED — CISA KEV

How to Fix CVE-2026-20131: Insecure Deserialization in Cisco Secure Firewall Management Center (FMC)

By Sai Kiran Pandrala

⚡ At a glance
SeverityCVSS 10 - Critical
Actively exploited?Yes, listed in CISA KEV (added 2026-03-19)
AffectedCisco Secure Firewall Management Center (FMC) 7.0.0; Cisco Secure Firewall Management Center (FMC) 7.0.0.1; Cisco Secure Firewall Management Center (FMC) 7.0.1; Cisco Secure Firewall Management Center (FMC) 7.1.0; see advisory for full list
Fixed inSee vendor advisory
Type (CWE)CWE-502: Deserialization of Untrusted Data

Patch immediately. CISA added CVE-2026-20131 to the Known Exploited Vulnerabilities catalog on 2026-03-19. Federal civilian agencies must remediate by 2026-03-22. Treat every internet-reachable instance as a priority patch.

What is CVE-2026-20131?

CVE-2026-20131 is an Insecure Deserialization flaw in Cisco Secure Firewall Management Center (FMC). It carries a CVSS base score of 10 (critical). CISA confirmed real-world exploitation by adding it to the Known Exploited Vulnerabilities catalog on 2026-03-19.

From the source record: 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 t...

Why it matters in practice: KEV-listed CVEs draw continuous internet-wide scanning. Any unpatched, internet-reachable installation is on borrowed time. The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of Cisco Secure Firewall Management Center (FMC) matches a version listed in the Affected row above.

From the device CLI:


show version
show inventory

How to fix CVE-2026-20131

Apply the vendor patch. Target the patched build listed on the vendor advisory. The runnable command set below covers the most common deployment patterns for Cisco Secure Firewall Management Center (FMC).

Cisco IOS / IOS XE / NX-OS


! Copy the patched image to flash and boot it
copy tftp: flash:
configure terminal
 boot system flash:<patched-image.bin>
 end
write memory
reload

! After reload, confirm:
show version | include System image|Version

Cisco install-mode (IOS XE)


install add file flash:<patched-image.bin> activate commit

After applying the patch

  1. Restart the service or device so the patched binary loads.
  2. Confirm the running version matches the Fixed in row using the verification command below.
  3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict management-plane exposure

Block public access to the admin interface at the perimeter. Allow only trusted jump hosts and bastion IPs.


# Cisco IOS example: ACL on the management VTY
configure terminal
ip access-list standard MGMT-ACL
 permit 10.10.10.0 0.0.0.255
 deny any log
line vty 0 4
 access-class MGMT-ACL in
 end
write memory

On Linux jump hosts in front of the appliance, drop traffic from anything outside the admin range:


sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.


show version | include System image|Version
show inventory

Expected: the running version matches See vendor advisory.

Also worth doing: pull recent log windows for any indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-20131 being exploited in the wild?

Yes. CISA added CVE-2026-20131 to the Known Exploited Vulnerabilities catalog on 2026-03-19. KEV listing means at least one confirmed real-world exploitation report exists.

Do I have to take downtime to patch?

For most Cisco Secure Firewall Management Center (FMC) deployments, the patched build needs a service restart or device reboot. HA pairs and clusters can roll the upgrade by patching the standby first, failing over, then patching the former primary.

Will a WAF or IDS rule alone close CVE-2026-20131?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

Why is CVE-2026-20131 rated critical?

The CVSS base score of 10 reflects network reach, low attack complexity, and high impact on confidentiality, integrity, and availability. That combination is what the rating model maps to critical.

References

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*