Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Unauthenticated Root RCE in Cisco Secure Firewall Management Center Web Interface

IdentifiersCVE-2026-20131CWE-502· Deserialization of Untrusted Data

CVE-2026-20131 is a critical insecure deserialization vulnerability in the web-based management interface of Cisco Secure Firewall Management Center (FMC) Software, and reporting also indicates impact to Cisco Security Cloud Control (SCC) Firewall Management. The flaw is caused by deserialization of a user-supplied Java byte stream without adequate validation. An unauthenticated remote attacker can exploit the issue by sending a crafted serialized Java object to the affected management interface. Successful exploitation results in arbitrary Java code execution on the target device and can lead to execution with root privileges. Cisco disclosed the issue on 2026-03-04 and later acknowledged active exploitation in the wild; multiple reports attribute exploitation to the Interlock ransomware group prior to public disclosure.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows full remote compromise of the affected management platform without authentication. Because code execution occurs as root, an attacker can take complete control of the FMC/SCC instance, alter firewall policies, disable or evade security controls, hide alerts, push malicious configurations, use the management plane as a pivot into managed environments, steal sensitive data, establish persistence, and ultimately support follow-on activity including lateral movement and ransomware deployment. The vulnerability has been reported as actively exploited in the wild, including in ransomware operations.

Mitigation

If you can’t patch tonight, do this now.

No temporary workaround is available for on-premises deployments according to Cisco. As an exposure-reduction measure, restrict or remove public internet access to the FMC management interface and tightly limit access to trusted administrative networks only; however, this is not a substitute for patching. If immediate remediation is not possible, organizations should isolate the management interface behind firewalls/VPNs, monitor for suspicious requests to the web management interface, review for unauthorized remote access tooling such as ScreenConnect, inspect for indicators of compromise, and consider temporarily discontinuing use of exposed vulnerable instances until secured.

Remediation

Patch, then assume compromise.

Apply Cisco’s fixed software releases immediately for on-premises Cisco Secure Firewall Management Center deployments. Use Cisco’s Software Checker and official advisory guidance to identify affected versions and upgrade paths. For SaaS-delivered Cisco Security Cloud Control Firewall Management, reporting indicates Cisco has already deployed fixes during routine maintenance and cloud customers generally do not need additional action beyond verification. Because the vulnerability is known exploited, remediation should be treated as urgent and incident response review should accompany patching where exposure existed.
PUBLIC EXPLOITS

Exploits

2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (3 hidden).

VALID 2 / 5 TOTALView more in app
CVE-2026-20131MaturityPoCVerified exploit

Repository contains a detection script and an RCE PoC for CVE-2026-20131 (Cisco Secure Firewall Management Center Java deserialization). Structure: (1) README.md documents the vulnerability, affected products, and usage. (2) check.py is a safe network probe that POSTs Java serialization magic bytes (0xACED0005) with Content-Type application/x-java-serialized-object to several FMC endpoints (/j_spring_security_check, /api/fmc_platform/v1/auth/generatetoken, /dispatcher, /invoker/JMXInvokerServlet, /invoker/EJBInvokerServlet) and flags HTTP 500/200 as potential deserialization handling. (3) poc.py is an operational PoC exploit that generates a malicious serialized object using an external tool (ysoserial-all.jar executed via local Java) with selectable gadget chains (CommonsCollections*, Spring*, Groovy1) and an attacker-supplied command, then POSTs the payload to likely deserialization endpoints. The exploit is unauthenticated and intended to achieve blind command execution (often inferred from HTTP 500 and/or out-of-band callbacks such as reverse shells or DNS). No persistence is implemented; payload is arbitrary command execution.

sak110Disclosed Mar 11, 2026pythonmarkdownnetwork
CVE-2026-20131-POCMaturityPoCVerified exploit

Repository contains a claimed working PoC exploit for CVE-2026-20131 targeting Cisco Catalyst SD-WAN Controller (vSmart) and Catalyst SD-WAN Manager (vManage). Structure: (1) `CVE-2026-20131-POC.py` is the main exploit entry point but is PyArmor-obfuscated/encrypted, preventing static extraction of exact request paths, parameters, or hardcoded targets from the provided content. (2) `cmd.jsp` is a JSP webshell payload that executes arbitrary OS commands supplied via the `cmd` HTTP parameter using `bash -c`, returning both stdout and stderr—indicative of post-exploitation persistence/command execution. (3) `README.md` describes capabilities: pre-auth auth bypass, admin privilege gain, ability to create a rogue peer in the SD-WAN control/management plane, and access to NETCONF on TCP/830. Fingerprintable observables available from the repo content are limited to the Telegram URL and the NETCONF port reference; any additional exploit endpoints (e.g., specific vManage/vSmart API paths) are likely embedded inside the obfuscated Python script and are not visible here.

p3Nt3st3r-sTArDisclosed Mar 6, 2026pythonjspnetwork (pre-authentication remote exploitation against Cisco SD-WAN management/control plane; likely leads to admin access/RCE)
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Cisco SystemsSecure Firewall Adaptive Security Applianceapplication
Cisco SystemsSecure Firewall Management Centerapplication
Cisco SystemsSecure Firewall Management Center Softwareapplication
Cisco SystemsSecure Firewall Threat Defense Softwareapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence9

Every observed campaign linking this CVE to a named adversary.

Associated malware10

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity173

Community discussion across Reddit, Mastodon, and other social sources.