[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fiRBn6_5-kNCwX7fVd7IvJSdFq0cvK402KQNFYUcB4i0":3},{"article":4,"iocs":42,"watch_terms":69,"solutions":70,"lesson":165},{"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":29,"category":30,"article_tags":34},"69617b01-fe59-4e64-aed4-24e064329b08","Cisco warns of critical flaws allowing Nexus switch takeover","cisco-warns-of-critical-flaws-allowing-nexus-switch-takeover-484d29","Cisco released security advisories for five critical vulnerabilities in its NX-OS data center network operating system that could be exploited to run arbitrary code with root privileges on Nexus switches. [...]","Cisco has issued advisories for five critical vulnerabilities in its NX-OS data center network operating system affecting Nexus 3000 and 9000 Series switches. Exploitation could lead to arbitrary code execution with root privileges or denial-of-service conditions. The vulnerabilities are rooted in input validation failures within features like NX-API, NGOAM, and MPLS OAM, and require specific features to be active for successful exploitation.","Cisco warns of five critical NX-OS flaws allowing Nexus switch takeover and RCE.","https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fcisco-warns-of-critical-flaws-allowing-nexus-switch-takeover\u002F","https:\u002F\u002Fwww.bleepstatic.com\u002Fcontent\u002Fhl-images\u002F2025\u002F03\u002F04\u002FCisco-headpic.jpg","2026-10-08T15:26:33+00:00","2026-10-08T16:00:27.052694+00:00",9,[17,20,23,25,27],{"name":18,"type":19},"NX-OS","product",{"name":21,"type":22},"Cisco","vendor",{"name":24,"type":19},"Nexus 3000 Series",{"name":26,"type":19},"Nexus 9000 Series",{"name":28,"type":19},"Cisco License","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":29,"icon":31,"name":32,"slug":33},null,"Vulnerabilities","vulnerabilities",[35,37],{"category":36},{"id":29,"icon":31,"name":32,"slug":33},{"category":38},{"id":39,"icon":31,"name":40,"slug":41},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[43,47,50,52,54,57,60,63,66],{"type":44,"value":45,"context":46},"cve","CVE-2026-76471","NX-API insufficient input validation",{"type":44,"value":48,"context":49},"CVE-2026-76485","NGOAM improper IP traffic validation",{"type":44,"value":51,"context":49},"CVE-2026-76486",{"type":44,"value":53,"context":49},"CVE-2026-76501",{"type":44,"value":55,"context":56},"CVE-2026-76465","MPLS OAM improper echo-request packet validation",{"type":44,"value":58,"context":59},"CVE-2026-76480","Cisco License missing authentication for critical functions",{"type":44,"value":61,"context":62},"CVE-2026-76482","Cisco License improper cryptographic signature verification",{"type":44,"value":64,"context":65},"CVE-2026-76483","Cisco License insufficiently protected credentials",{"type":44,"value":67,"context":68},"CVE-2026-76484","Cisco License code injection",[21,18,24],{"controls":71,"vendors":159},[72,101,130],{"slug":73,"name":74,"problem":75,"products":76},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[77,85,93],{"vendor_slug":78,"vendor_name":79,"vendor_logo":80,"product_slug":81,"product_name":82,"url":83,"description":84},"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":86,"vendor_name":87,"vendor_logo":88,"product_slug":89,"product_name":90,"url":91,"description":92},"tenable","Tenable","\u002Fvendor-logos\u002Ftenable.png","tenable-vulnerability-management","Tenable Vulnerability Management","https:\u002F\u002Fwww.tenable.com\u002Fproducts\u002Fvulnerability-management","Cloud-based vulnerability scanning and prioritisation, built on Nessus.",{"vendor_slug":94,"vendor_name":95,"vendor_logo":96,"product_slug":97,"product_name":98,"url":99,"description":100},"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.",{"slug":102,"name":103,"problem":104,"products":105},"patch-management","Automated patch management","Known holes get closed in days, not months.",[106,114,122],{"vendor_slug":107,"vendor_name":108,"vendor_logo":109,"product_slug":110,"product_name":111,"url":112,"description":113},"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":115,"vendor_name":116,"vendor_logo":117,"product_slug":118,"product_name":119,"url":120,"description":121},"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.",{"vendor_slug":123,"vendor_name":124,"vendor_logo":125,"product_slug":126,"product_name":127,"url":128,"description":129},"action1","Action1","\u002Fvendor-logos\u002Faction1.png","action1-patch-management","Action1 Patch Management","https:\u002F\u002Fwww.action1.com\u002F","Cloud-native patch management for Windows, macOS and third-party applications.",{"slug":131,"name":132,"problem":133,"products":134},"network-segmentation","Network segmentation and microsegmentation","One compromised machine can no longer reach everything else.",[135,143,151],{"vendor_slug":136,"vendor_name":137,"vendor_logo":138,"product_slug":139,"product_name":140,"url":141,"description":142},"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":144,"vendor_name":145,"vendor_logo":146,"product_slug":147,"product_name":148,"url":149,"description":150},"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.",{"vendor_slug":152,"vendor_name":153,"vendor_logo":154,"product_slug":155,"product_name":156,"url":157,"description":158},"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.",[160],{"slug":161,"name":21,"logo_path":162,"roles":163},"cisco","\u002Fvendor-logos\u002Fcisco.png",[164],"affected",{"slug":166,"title":167,"body":168,"framework_refs":169,"framework_notes":180},"critical-cisco-nx-os-flaws-enable-root-level-switch-takeover","Critical Cisco NX-OS Flaws Enable Root-Level Switch Takeover","Five critical vulnerabilities in Cisco's NX-OS operating system expose Nexus 3000 and 9000 Series switches to arbitrary code execution with root privileges and denial-of-service attacks, stemming from inadequate input validation in key features like NX-API, NGOAM, and MPLS OAM. The root cause — poor input validation — is a foundational software security failure that should be caught during development and pre-release testing. What makes this especially dangerous is that these are core data center switches; a successful takeover could give an attacker full control over network infrastructure, enabling traffic interception, lateral movement, or complete outages. Organizations running these devices must treat this as a critical-priority remediation, particularly since the attack surface is narrowed only by whether specific features are enabled — a configuration detail many teams may not actively track.",[170,171,172,173,174,175,176,177,178,179],"CIS Control 7: Continuous Vulnerability Management","CIS Control 12: Network Infrastructure Management","CIS Control 4: Secure Configuration of Enterprise Assets","NIST SP 800-40 Rev. 4: Guide to Enterprise Patch Management","NIST SI-10: Information Input Validation","NIST CM-6: Configuration Settings","NIST CM-7: Least Functionality","NIST RA-5: Vulnerability Monitoring and Scanning","ITIL: Change and Release Management (patching workflows)","ISO\u002FIEC 27001 A.12.6.1: Management of Technical Vulnerabilities",{"NIST CM-7: Least Functionality":181,"NIST CM-6: Configuration Settings":182,"NIST SI-10: Information Input Validation":183,"NIST RA-5: Vulnerability Monitoring and Scanning":184,"CIS Control 12: Network Infrastructure Management":185,"CIS Control 7: Continuous Vulnerability Management":186,"CIS Control 4: Secure Configuration of Enterprise Assets":187,"ITIL: Change and Release Management (patching workflows)":188,"NIST SP 800-40 Rev. 4: Guide to Enterprise Patch Management":189,"ISO\u002FIEC 27001 A.12.6.1: Management of Technical Vulnerabilities":190},"Least functionality means turning off unused services like NX-API that expose switches to these flaws.","Configuration settings that disable unneeded features reduce the attack surface of Nexus switches.","Input validation flaws in NX-API, NGOAM and MPLS OAM are the root cause, which this control addresses.","Vulnerability scanning helps identify Nexus switches still running vulnerable NX-OS versions.","Network infrastructure management keeps core switches updated and their management features restricted.","Vulnerability management ensures the five critical NX-OS flaws are patched quickly across Nexus switches.","Secure configuration includes disabling unused features like NX-API, reducing exposure to these flaws.","Change and release management supports planned switch upgrades without disrupting the network.","Patch management planning should prioritise critical switch updates while managing outage risk.","Managing technical vulnerabilities includes rapid response to critical flaws in core network devices."]