[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"focus:n-able-patches-max-severity-n-central-flaw-amid-ongoing-attacks-mtrun6mq":3},{"item":4},{"id":5,"title":6,"slug":7,"summary":8,"severity":9,"category":10,"cve_ids":11,"affected_products":15,"action_required":19,"article_ids":20,"ioc_summary":22,"source_urls":23,"status":25,"expires_at":26,"created_at":27,"updated_at":28,"articles":29},"7921db0c-bab9-4fec-9215-da3098ea1604","N-able patches max severity N-central flaw amid ongoing attacks","n-able-patches-max-severity-n-central-flaw-amid-ongoing-attacks-mtrun6mq","N-able has released emergency patches for three vulnerabilities in N-central RMM, including a critical unauthenticated RCE (CVE-2026-86218) and two high-severity authentication bypasses. Evidence indicates active exploitation in customer environments. Any organization running N-central is at immediate risk of full system compromise.","critical","advisory",[12,13,14],"CVE-2026-86218","CVE-2026-86206","CVE-2026-86207",[16,17,18],"N-central","N-able","N-central 2026.3 Hotfix 4","Immediately patch N-central to the latest version. For any instances you cannot patch within 24 hours, isolate them from production networks and implement network-based access controls. Scan all N-central logs for exploitation indicators and check for lateral movement from affected systems.",[21],"a97204fe-fdec-4176-9e13-4d3e65accb93",null,[24],"https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fn-able-patches-max-severity-n-central-flaw-amid-ongoing-attacks\u002F","active","2026-09-09T23:05:49.349+00:00","2026-09-07T23:05:54.842355+00:00","2026-09-07T23:07:46.623405+00:00",[30],{"id":21,"title":6,"url":24}]