[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fim2n61Zle6ohfFDVarpy2CjaQvpnOuJCyTVlK2Hq0DQ":3},{"article":4,"iocs":50,"iocs_total":66,"watch_terms":67,"solutions":68,"lesson":163},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":27,"category":28,"article_tags":32},"f7e3c478-c7c7-45da-b729-26cbb7002070","CVE-2026-20131: Cisco FMC RCE Exploited by Interlock","cve-2026-20131-cisco-fmc-rce-exploited-by-interlock-4ed666","Patching is not enough: any Cisco FMC that ran vulnerable software after January 26 needs a compromise check against Amazon's Interlock indicators.","The Interlock ransomware group exploited CVE-2026-20131, a critical RCE vulnerability in Cisco Secure Firewall Management Center (FMC), for over five weeks before a patch was released. The flaw, an insecure deserialization bug, allowed unauthenticated attackers to execute arbitrary Java code as root, potentially compromising all managed Cisco firewalls. Cisco disclosed and patched the vulnerability on March 4, 2026, but Amazon's threat intelligence indicated exploitation began as early as January 26.","Interlock ransomware exploits Cisco FMC RCE flaw CVE-2026-20131, impacting devices since January 26.","https:\u002F\u002Fwww.cyberkendra.com\u002F2026\u002F11\u002Fcve-2026-20131-cisco-fmc-rce-interlock-ransomware.html","https:\u002F\u002Fwww.cyberkendra.com\u002Fwp-content\u002Fuploads\u002F2026\u002F09\u002Fcisco-flaw-1024x711.jpg","2026-11-15T16:25:18+00:00","2026-11-15T17:00:11.534619+00:00",9,[17,20,23,25],{"name":18,"type":19},"Secure Firewall Management Center","product",{"name":21,"type":22},"Cisco","vendor",{"name":24,"type":19},"Security Cloud Control",{"name":26,"type":22},"Amazon","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":27,"icon":29,"name":30,"slug":31},null,"Vulnerabilities","vulnerabilities",[33,38,43,45],{"category":34},{"id":35,"icon":29,"name":36,"slug":37},"6cbdd207-aaa1-4176-9534-e156b125e917","Nation-state","nation-state",{"category":39},{"id":40,"icon":29,"name":41,"slug":42},"7d8b5ab8-ea0b-4ced-ae97-ec251b86993a","Ransomware","ransomware",{"category":44},{"id":27,"icon":29,"name":30,"slug":31},{"category":46},{"id":47,"icon":29,"name":48,"slug":49},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[51,55,59,63],{"type":52,"value":53,"context":54},"malware","Interlock","Ransomware group exploiting CVE-2026-20131",{"type":56,"value":57,"context":58},"cve","CVE-2026-20131","Remote code execution flaw in Cisco Secure Firewall Management Center (FMC)",{"type":60,"value":61,"context":62},"ip","206.251.239.164","Written defanged in the article text",{"type":64,"value":65,"context":62},"domain","cherryberry.click",4,[21,26,18],{"controls":69,"vendors":156},[70,99,127],{"slug":71,"name":72,"problem":73,"products":74},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[75,83,91],{"vendor_slug":76,"vendor_name":77,"vendor_logo":78,"product_slug":79,"product_name":80,"url":81,"description":82},"holm-security","Holm Security","\u002Fvendor-logos\u002Fholm-security.png","holm-security-platform","Holm Security Platform","https:\u002F\u002Fwww.holmsecurity.com\u002F","Vulnerability scanning of systems, web applications, cloud and the external attack surface, plus phishing simulation.",{"vendor_slug":84,"vendor_name":85,"vendor_logo":86,"product_slug":87,"product_name":88,"url":89,"description":90},"rapid7","Rapid7","\u002Fvendor-logos\u002Frapid7.png","insightvm","Rapid7 Exposure Command (InsightVM)","https:\u002F\u002Fwww.rapid7.com\u002Fproducts\u002Finsightvm\u002F","Vulnerability scanning and risk-based prioritisation; InsightVM is now part of Exposure Command, alongside attack surface and cloud risk.",{"vendor_slug":92,"vendor_name":93,"vendor_logo":94,"product_slug":95,"product_name":96,"url":97,"description":98},"axonius","Axonius","\u002Fvendor-logos\u002Faxonius.png","axonius-exposures","Axonius Exposures","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fexposures","Brings findings from different scanners together with asset and business context, to show what matters most and track fixes to the end.",{"slug":100,"name":101,"problem":102,"products":103},"patch-management","Automated patch management","Known holes get closed in days, not months.",[104,111,119],{"vendor_slug":105,"vendor_name":106,"vendor_logo":107,"product_slug":100,"product_name":108,"url":109,"description":110},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","Qualys Patch Management","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fpatch-management\u002F","Patch deployment for operating systems and third-party applications, linked to vulnerability findings.",{"vendor_slug":112,"vendor_name":113,"vendor_logo":114,"product_slug":115,"product_name":116,"url":117,"description":118},"manageengine","ManageEngine","\u002Fvendor-logos\u002Fmanageengine.png","patch-manager-plus","ManageEngine Patch Manager Plus","https:\u002F\u002Fwww.manageengine.com\u002Fpatch-management\u002F","Patch management for operating systems and third-party applications, on premises or in the cloud.",{"vendor_slug":120,"vendor_name":121,"vendor_logo":122,"product_slug":123,"product_name":124,"url":125,"description":126},"ninjaone","NinjaOne","\u002Fvendor-logos\u002Fninjaone.png","ninjaone-patch-management","NinjaOne Patch Management","https:\u002F\u002Fwww.ninjaone.com\u002Fpatch-management\u002F","Automated patching of operating systems and third-party applications from the cloud.",{"slug":128,"name":129,"problem":130,"products":131},"network-segmentation","Network segmentation and microsegmentation","One compromised machine can no longer reach everything else.",[132,140,148],{"vendor_slug":133,"vendor_name":134,"vendor_logo":135,"product_slug":136,"product_name":137,"url":138,"description":139},"akamai","Akamai","\u002Fvendor-logos\u002Fakamai.png","guardicore-segmentation","Akamai Guardicore Segmentation","https:\u002F\u002Fwww.akamai.com\u002Fproducts\u002Fakamai-guardicore-segmentation","Software-based microsegmentation with traffic visibility.",{"vendor_slug":141,"vendor_name":142,"vendor_logo":143,"product_slug":144,"product_name":145,"url":146,"description":147},"threatlocker","ThreatLocker","\u002Fvendor-logos\u002Fthreatlocker.png","zero-trust-endpoint-firewall","Zero Trust Endpoint Firewall","https:\u002F\u002Fwww.threatlocker.com\u002Fcapabilities\u002Fzero-trust-endpoint-firewall","Centrally managed host firewall with device-level and dynamic access rules, to limit which machines can talk to each other.",{"vendor_slug":149,"vendor_name":150,"vendor_logo":151,"product_slug":152,"product_name":153,"url":154,"description":155},"illumio","Illumio","\u002Fvendor-logos\u002Fillumio.png","illumio-segmentation","Illumio Segmentation","https:\u002F\u002Fwww.illumio.com\u002Fillumio-segmentation","Maps traffic between workloads and enforces segmentation across data centre, cloud and endpoints.",[157],{"slug":158,"name":21,"logo_path":159,"roles":160},"cisco","\u002Fvendor-logos\u002Fcisco.png",[161,162],"affected","reported_by",{"slug":164,"title":165,"body":166,"framework_refs":167,"framework_notes":173},"zero-day-rce-in-cisco-fmc-exploited-for-5-weeks-before-patch","Zero-Day RCE in Cisco FMC Exploited for 5+ Weeks Before Patch","The Interlock ransomware group exploited an insecure deserialization vulnerability in Cisco's Firewall Management Center for over five weeks before Cisco released a patch, giving attackers unauthenticated root-level code execution on a system responsible for managing an entire firewall estate. The core problem was the gap between when exploitation began (January 26) and when the patch became available (March 4) — a window that organizations had no vendor-supplied fix to close. This matters because a compromised FMC doesn't just affect one device; it can cascade to every managed firewall beneath it, effectively nullifying an organization's entire perimeter defense. The incident underscores how critical network management planes must be isolated and monitored aggressively, especially when vendor patches are unavailable.",[168,169,170,171,172],"CIS Control 7: Continuous Vulnerability Management (v8)","CIS Control 12: Network Infrastructure Management (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 RS.AN-03: Analysis of incidents","NIS2 Article 21(2)(e)",{"NIS2 Article 21(2)(e)":174,"NIST SP 800-53 SI-2: Flaw Remediation":175,"NIST CSF 2.0 RS.AN-03: Analysis of incidents":176,"CIS Control 12: Network Infrastructure Management (v8)":177,"CIS Control 7: Continuous Vulnerability Management (v8)":178},"NIS2 Article 21(2)(e) explicitly covers vulnerability handling and disclosure in the acquisition and maintenance of systems, requiring entities to have processes for managing vulnerabilities — including compensating measures during zero-day windows like this one.","SI-2 requires organizations to identify, report, and correct system flaws within defined timeframes, and to establish interim safeguards when patches are not yet available — directly addressing the five-week unpatched exposure window.","Threat intelligence indicated exploitation began January 26, but organizations without active threat-intel integration would have missed this signal; RS.AN-03 calls for analyzing threat intelligence to inform incident response before formal disclosure.","CIS Control 12 requires securing and managing network infrastructure devices, which would have mandated isolating the FMC console from internet exposure and limiting the blast radius of an RCE on the management plane.","CIS Control 7 requires organizations to continuously assess and remediate vulnerabilities; a formal process here would have prompted compensating controls the moment exploitation-in-the-wild intelligence emerged, weeks before the patch was available."]