[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fIevHwJG7XeRmUbJqmD6D6QuSnvhdMH870rL28pD8loQ":3},{"article":4,"iocs":51,"watch_terms":52,"solutions":53,"lesson":139},{"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":28,"category":29,"article_tags":33},"b3664566-c781-44cd-8c6c-803d3dfddbc6","N-able Releases Emergency N-central Hotfix After 33 Vulnerabilities Trigger Worldwide Cloud Shutdown","n-able-releases-emergency-n-central-hotfix-after-33-vulnerabilities-trigger-worl-a71d23","N-able has released N-central 2026.4 Hotfix 2 after the public disclosure of 33 alleged vulnerabilities forced a worldwide shutdown of its hosted remote monitoring and management platform. Released on November 10, the emergency update, build 2026.4.1.26, fixes seven published CVEs and adds security changes across the server, Agents, and Probes. The shutdown began on November […] The post N-able Releases Emergency N-central Hotfix After 33 Vulnerabilities Trigger Worldwide Cloud Shutdown appeared first on Cyber Security News.","N-able has released N-central 2026.4 Hotfix 2 to address 33 alleged vulnerabilities that led to a worldwide shutdown of its hosted remote monitoring and management platform. The emergency update fixes seven published CVEs and includes security enhancements across server, Agents, and Probes. The shutdown, which began on November 9, affected hosted services globally, and N-able advised customers with self-hosted servers to take them offline.","N-able releases emergency hotfix after 33 vulnerabilities trigger worldwide cloud shutdown.","https:\u002F\u002Fcybersecuritynews.com\u002Fn-able-n-central-security-vulnerabilities\u002F","https:\u002F\u002Fcybersecuritynews.com\u002Fwp-content\u002Fuploads\u002F2026\u002F11\u002FN-able-N-central-vulnerabilities.webp","2026-11-11T12:57:12+00:00","2026-11-11T13:00:24.780829+00:00",8,[17,20,23,26],{"name":18,"type":19},"N-central","product",{"name":21,"type":22},"N-able","vendor",{"name":24,"type":25},"remote monitoring and management","technology",{"name":27,"type":19},"Take Control","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":28,"icon":30,"name":31,"slug":32},null,"Vulnerabilities","vulnerabilities",[34,39,41,46],{"category":35},{"id":36,"icon":30,"name":37,"slug":38},"26b0b636-0e31-4db1-bffb-61bdf9f20a58","Supply Chain","supply-chain",{"category":40},{"id":28,"icon":30,"name":31,"slug":32},{"category":42},{"id":43,"icon":30,"name":44,"slug":45},"c5eccf7c-abbc-4bd3-bbed-e6da5cba8e73","Incident Response","incident-response",{"category":47},{"id":48,"icon":30,"name":49,"slug":50},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[],[21,18,27],{"controls":54,"vendors":138},[55,84,113],{"slug":56,"name":57,"problem":58,"products":59},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[60,68,76],{"vendor_slug":61,"vendor_name":62,"vendor_logo":63,"product_slug":64,"product_name":65,"url":66,"description":67},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","vmdr","Qualys VMDR","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fvulnerability-management-detection-response\u002F","Vulnerability management, detection and response with risk-based prioritisation.",{"vendor_slug":69,"vendor_name":70,"vendor_logo":71,"product_slug":72,"product_name":73,"url":74,"description":75},"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":77,"vendor_name":78,"vendor_logo":79,"product_slug":80,"product_name":81,"url":82,"description":83},"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":85,"name":86,"problem":87,"products":88},"patch-management","Automated patch management","Known holes get closed in days, not months.",[89,97,105],{"vendor_slug":90,"vendor_name":91,"vendor_logo":92,"product_slug":93,"product_name":94,"url":95,"description":96},"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":98,"vendor_name":99,"vendor_logo":100,"product_slug":101,"product_name":102,"url":103,"description":104},"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.",{"vendor_slug":106,"vendor_name":107,"vendor_logo":108,"product_slug":109,"product_name":110,"url":111,"description":112},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png","intune","Microsoft Intune","https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fbusiness\u002Fmicrosoft-intune","Device management for Windows, macOS, iOS and Android, including update rings and compliance policies.",{"slug":114,"name":115,"problem":116,"products":117},"asset-inventory","Cyber asset inventory","You cannot patch, monitor or protect the devices, cloud resources and accounts you do not know you have.",[118,125,130],{"vendor_slug":119,"vendor_name":120,"vendor_logo":121,"product_slug":122,"product_name":120,"url":123,"description":124},"lansweeper","Lansweeper","\u002Fvendor-logos\u002Flansweeper.png","lansweeper-asset-inventory","https:\u002F\u002Fwww.lansweeper.com\u002Fproduct\u002Fasset-inventory\u002F","Discovery with and without agents that keeps one central, always-updated inventory of devices, software and their details.",{"vendor_slug":77,"vendor_name":78,"vendor_logo":79,"product_slug":126,"product_name":127,"url":128,"description":129},"axonius-cyber-assets","Axonius Cyber Assets","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fcyber-assets","A continuously reconciled view of every asset, who owns it, which security controls cover it and where it drifts from policy.",{"vendor_slug":131,"vendor_name":132,"vendor_logo":133,"product_slug":134,"product_name":135,"url":136,"description":137},"runzero","runZero","\u002Fvendor-logos\u002Frunzero.png","runzero-platform","runZero Platform","https:\u002F\u002Fwww.runzero.com\u002Fplatform\u002F","Finds and fingerprints everything on the network and in the cloud, including IoT and OT devices, without agents or credentials, and flags exposures.",[],{"slug":140,"title":141,"body":142,"framework_refs":143,"framework_notes":149},"33-unpatched-vulnerabilities-trigger-global-rmm-platform-shutdown","33 Unpatched Vulnerabilities Trigger Global RMM Platform Shutdown","N-able's hosted N-central platform was forced into a worldwide emergency shutdown after 33 alleged vulnerabilities were identified, including seven published CVEs, across its remote monitoring and management infrastructure. The severity of the exposure was significant enough that N-able also advised customers running self-hosted instances to take their servers offline immediately — a rare and disruptive step. This incident illustrates the outsized risk posed by vulnerabilities in RMM platforms, which by design hold privileged access to thousands of managed endpoints. The scale of disruption underscores that vulnerability accumulation in critical management infrastructure can cascade into a global service outage with far-reaching consequences for managed service providers and their downstream clients.",[144,145,146,147,148],"CIS Control 7: Continuous Vulnerability Management (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 ID.RA-1: Asset vulnerabilities are identified and documented","NIS2 Article 21(2)(e)","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities",{"NIS2 Article 21(2)(e)":150,"NIST SP 800-53 SI-2: Flaw Remediation":151,"CIS Control 7: Continuous Vulnerability Management (v8)":152,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":153,"NIST CSF 2.0 ID.RA-1: Asset vulnerabilities are identified and documented":154},"NIS2 Article 21(2)(e) addresses vulnerability handling and disclosure in acquisition, development, and maintenance; N-able's accumulation of 33 vulnerabilities before emergency action points to gaps in systematic vulnerability handling obligations applicable to critical service providers.","SI-2 requires organizations to identify, report, and correct information system flaws in a timely manner; enforcing flaw remediation SLAs on the N-central platform would have prevented the accumulation of 33 unaddressed vulnerabilities.","CIS Control 7 requires organizations to continuously assess and remediate vulnerabilities; applying a structured vulnerability management process to N-central would have identified and addressed the 33 CVEs before they forced a global shutdown.","A.8.8 requires organizations to obtain timely information about technical vulnerabilities and take appropriate measures; a formal process under this control would have driven earlier detection and patching of the CVEs that caused the N-central outage.","This category requires that vulnerabilities across assets be identified and tracked; proactive identification of the CVEs in N-central's server, Agent, and Probe components could have enabled remediation before a forced global shutdown became necessary."]