Skip to main content

CVE-2026-20131Cisco Secure Firewall Management Center (FMC) Software and Cisco Security Cloud Control (SCC) Firewall Management Deserialization of Untrusted Data Vulnerability

Patch nowCritical10.0Exploited, CISA due date 2026-03-22EPSS 44%, higher than 99% of scored CVEs

CVE-2026-20131 is a deserialization of untrusted data in Cisco Secure Firewall Management Center (FMC), rated critical (10.0 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published · Updated · NVD status: Analyzed

What it is

Serialized objects from outside are turned back into live objects, which a crafted payload can abuse to run code.

How it is reached

An attacker can exploit it over the network, without an account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker turn crafted data into code execution inside the receiving service. The damage can spread past the vulnerable component into others.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2026-03-19: it is being exploited in the wild. CISA links it to ransomware campaigns. It can be exploited automatically, at scale. EPSS estimates a 44% chance of exploitation activity in the next 30 days, higher than 99% of scored CVEs.

What to do

  1. Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2026-03-22.
  2. No fixed version is listed yet. Find every place Cisco Secure Firewall Management Center (FMC) runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  3. While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
  4. Check exposed instances for signs of compromise, not only for the version.

Description from NVD

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 the FMC management interface does not have public internet access, the attack surface that is associated with this vulnerability is reduced.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Network edge devices: VPNs, firewalls, routers and gateways. They sit between the internet and internal networks, so a flaw in one is often the first step into everything behind it.
  • APIs, queues and caches that accept serialized objects. The flaw sits between a message producer and the service that deserializes it.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • Between a message producer and the service that deserializes it. An attacker who crosses it can turn crafted data into code execution inside the receiving service.

Questions to answer about your own systems

  • Where does Cisco Secure Firewall Management Center (FMC) run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.