N-able's N-central flaws: what to ask your MSP this week

By DataForge team18 November 20265 min read

Attackers exploited N-able N-central's Able2Shell flaws within hours. Here's what NZ firms should check with their MSP or in-house RMM team now.

What happened to N-central

Late on Sunday 8 November (US time), researcher Sean Bales published proof-of-concept exploits for more than 30 flaws in N-able's N-central, according to BleepingComputer. N-central is a remote monitoring and management (RMM) platform. Managed service providers (MSPs) use it to patch, script and remotely control their clients' computers. On 9 November N-able took its hosted N-central environments offline in the Americas, Europe and Asia-Pacific and told on-premises customers to shut down their own servers. Bales told BleepingComputer he skipped private disclosure because flaws he'd reported in a different N-able product months earlier were still unpatched.

N-able shipped Hotfix 2 on 10 November and brought hosted servers back online. On 11 November Bales released two more exploit sets, 4EverAble2Shell and Agent2Shell, and Huntress reports that both worked against the patched build. Attackers moved quickly. BleepingComputer cites threat researchers at Huntback, who counted at least 21 production N-central servers running an XMRig cryptominer on 12 November. Nineteen of those servers were on the Hotfix 2 build. The 4EverAble2Shell attack needs N-central's Legacy API to be switched on and reachable from the internet. N-able says that setting is off by default.

On 12 November N-able restricted features, switched off the Intune integration and later published indicators of compromise. The incident page lists both hosted and on-premises N-central in the APAC region among the affected services. Hotfix 3 was delivered at 5pm US Eastern time on 16 November, which was 11am on 17 November in New Zealand. The hotfix fixes 17 CVEs and permanently removes the Legacy API. It also disables remote control other than Take Control and blocks the Intune integration until a later release. Huntress says N-able published CVSS 4.0 scores on 17 November, with three flaws rated critical at 9.2 or 9.3. Public exploit code for all 17 CVEs appeared the evening Hotfix 3 shipped. As of 17 November, Huntress hadn't seen those flaws exploited in its partners' environments.

Why an RMM server is a bigger target than most

An RMM server holds administrator-level reach into every machine it manages. Its agents run with SYSTEM privileges on Windows endpoints, and its automation policies often contain stored credentials. Huntress describes Agent2Shell chains that let an unauthenticated attacker who can reach the server run commands as SYSTEM on managed Windows machines. CVE-2026-129275 allowed anyone to download Automation Manager policies, including embedded scripts and secrets, without logging in. The confirmed attacks so far installed cryptominers, which is a mild result. BleepingComputer notes that the same access could be turned against every customer environment the server manages.

Able2Shell is also the third serious N-central security event of 2026. Huntress lists authentication bypass flaws in August and a CVSS 10.0 zero-day that was actively exploited in September. The wider RMM market had a rough week too. In the same week's security roundup, ConnectWise disabled extensions across about 400 customer environments after a ScreenConnect campaign, and Huntress counted at least six MSPs breached.

What it means for NZ businesses

Most New Zealand small and mid-sized firms never log into N-central. They reach the platform through an MSP, so their exposure depends on a supplier relationship they may never have examined closely. Plenty of business owners couldn't name the RMM tool installed on their staff laptops. Few know whether their MSP runs the tool on its own server or in the vendor's cloud, or how quickly the MSP applies vendor hotfixes. Those three facts decided how exposed a business was between 8 and 17 November.

The outage carries its own operational cost. While N-central was offline, MSPs on the platform lost their usual tools for patching, scripting and remote support. Service desks fell back on slower methods, and ticket queues and SLA clocks didn't stop for the vendor's incident. Hotfix 3 keeps some remote control functions and the Intune integration switched off for now, so a few workflows will stay degraded after the patch goes on.

Organisations that run N-central in-house have more direct work to do. Patching the server alone won't close the agent impersonation issues. Huntress's guidance covers the whole stack: the server on build 2026.4.1.39, every agent and probe on Hotfix 3, and the Patch Management Engine on 2.14.4.5829 or later.

In ITIL 4 terms, Able2Shell tests supplier management, information security management and change enablement all at once. A supplier's emergency shutdown triggered your incident process, whether or not your contract anticipated one. Our ITIL 4 framework guidance covers how to bring third-party tooling into those practices so the next RMM incident lands on a documented plan.

Practical next steps

  • Ask your MSP four questions in writing. Do they use N-central, and is it hosted or on-premises? What build are the server and agents on today? Was the Legacy API ever enabled and internet-facing, especially from 11 November onward?
  • Ask what checks the MSP ran. N-able and Huntress have published indicators of compromise, including outbound traffic to 157.20.241[.]16 and unexpected PowerShell spawned by the N-able agent. Ask whether your MSP has searched for them and what they found.
  • Rotate secrets held in RMM automation. If an MSP's server was exposed before patching, any passwords or API keys stored in its Automation Manager policies should be treated as leaked. That includes credentials for your systems.
  • Enforce MFA on every RMM console account. Huntress notes that one of the fixed flaws allowed account email enumeration, so attackers may already hold valid usernames.
  • Audit remote access tools on your endpoints. List every RMM and remote support agent installed across your fleet and remove any your current provider doesn't account for. Old agents from a previous MSP are a common gap.
  • Add a supplier security notification clause. Your MSP contract should say how fast the provider tells you about a security incident in its own tooling and what evidence it'll share afterwards.
  • Write a fallback for when the RMM is down. Record how urgent patches, new starters and password resets will be handled if the management platform is offline for several days, then test that plan once a year.
  • Log the event in your risk register. Record the dates, your MSP's response and any residual gaps. The record will help at contract renewal and with your cyber insurer.

For firms that want to automate those supplier checks and asset audits, our process and automation team can help design the workflow.

Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.

Get my free assessment How we help
Get new articles by RSS