Skip to content
Bellator Cyber Guard
News4 min readQuick Read

N-able Patches 17 N-central Bugs After Miner Attacks

By Bellator Cyber Guard Security Team
N-able Patches 17 N-central Bugs After Miner Attacks - central hotfix flaws patches update 2026

N-able Ships Third Critical Hotfix for N-central Platform

N-able has released N-central 2026.4 Hotfix 3, a critical security update that patches 17 vulnerabilities in its Remote Monitoring and Management (RMM) and Unified Endpoint Management (UEM) platform, according to the official N-able status page release notes published November 16, 2026. N-central is software that managed service providers (MSPs) and internal IT teams use to remotely monitor, patch, and control endpoints such as servers, workstations, and network devices across client environments. Because a single N-central server often has administrative reach into many client networks at once, flaws in the platform carry outsized risk for every business an affected MSP serves.

The hotfix, built as version 2026.4.1.39, fixes 17 newly tracked CVEs covering authentication bypasses, missing authorization checks, server-side request forgery, XML external entity injection, a path traversal flaw N-able says leads to remote code execution, and a syslog injection bug the company says allows root command execution. The release notes list the full set, including CVE-2026-129271 (local privilege escalation in Patch Management), CVE-2026-129272 (an authentication bypass in the MMS3 appliance tied to a predictable passcode), and CVE-2026-129286 (a path traversal issue in SIS GenericFiles leading to remote code execution).

N-able says Hotfix 3 also permanently removes the configuration option for legacy APIs, blocking them outright, and tightens how Agents and Probes authenticate and communicate with the N-central server. The company states in its release notes that Agents and Probes which are not upgraded remain susceptible to impersonation. The release notes also describe this hotfix as building on, and superseding, Hotfix 1 and Hotfix 2, though no release dates for those two earlier hotfixes were provided in the supplied material.

An Earlier Flaw Set Is Already Being Exploited for Crypto Mining

Hotfix 3 arrives days after N-able began restricting certain N-central features following disclosure of two vulnerability sets known as 4EverAble2Shell and Agent2Shell, reported by The Hacker News on November 17, 2026. Independent security researcher Sean Bales, credited in that report with disclosing the flaws, reportedly published additional technical detail covering 24 CVEs and said the patched vulnerabilities should not work on the latest patch.

According to the same report, both 4EverAble2Shell and Agent2Shell can let an attacker run arbitrary code as root or gain SYSTEM-level access on Windows systems under specific conditions, and exploitation of 4EverAble2Shell depends on legacy API mode being enabled, the same mode N-able has now permanently blocked in Hotfix 3. The report states that 4EverAble2Shell specifically has come under active exploitation, with attackers using it to install cryptocurrency mining software on vulnerable N-central servers. The supplied reporting does not describe Agent2Shell as actively exploited; that flaw set is reported as disclosed and patched, not as a source of the mining activity. Bellator Cyber Guard has not independently verified the scope or number of affected servers; this claim rests on that single report and the researcher's disclosure, not on an N-able advisory confirming active exploitation.

Key Takeaway

If your organization outsources IT management to an MSP, ask directly whether that MSP runs N-able N-central and whether it has applied Hotfix 3 (build 2026.4.1.39) and upgraded every Agent and Probe. An unpatched or partially patched N-central server sitting between your business and its endpoints is a single point of failure that attackers are reportedly already probing through the 4EverAble2Shell flaws for cryptojacking, and the same access could be repurposed for more damaging intrusions.

What This Means For Your Business

Most healthcare practices, tax offices, and small businesses never interact with N-central directly; their MSP does. That makes this a supply-chain exposure: the vulnerability sits one layer removed from your own systems, inside software your IT vendor controls. A compromised N-central server can give an attacker the same administrative reach the MSP has, including the ability to push software, read stored credentials, or move into client networks.

If you rely on an MSP:

  • Ask your MSP in writing whether they run N-able N-central, and whether their on-premise server has been upgraded to build 2026.4.1.39 (Hotfix 3) with all Agents and Probes updated.
  • Ask whether they have reviewed logs for unexplained CPU usage spikes on managed servers and endpoints, the symptom associated with the 4EverAble2Shell cryptocurrency mining activity described in the November 2026 report.
  • Confirm your service agreement spells out who is responsible for patching timelines on the RMM platform itself, not just the endpoints it manages.

If you run N-central on-premise or manage it for clients:

  • Upgrade the N-central server to build 2026.4.1.39 as soon as possible; hosted (NCOD) customers are patched automatically by N-able and do not need to take server-side action.
  • Upgrade every Agent and Probe regardless of hosting model. N-able warns that any Agent or Probe left on an older version remains susceptible to impersonation even after the server is patched.
  • Plan around two known issues in Hotfix 3: remote control functionality other than Take Control is currently disabled, and Intune integration is blocked. Build that into change management and client communication before you patch.
  • After upgrading, check the new Inactive Assets tab under Configuration, Asset Discovery, Discovered Assets for devices that may need an administrator to manually restore the correct active Agent, particularly cloned, re-imaged, or recently restored machines.

The broader lesson is not specific to N-able. RMM and UEM platforms are high-value targets precisely because they are built for broad, automated reach into client systems. Any organization that grants a vendor this level of access should treat that vendor's patch cadence and disclosure practices as part of its own risk posture, not someone else's problem.

Share

Share on X
Share on LinkedIn
Share on Facebook
Send via Email
Copy URL
(800) 492-6076

See whether the service fits

Choose a security approach that fits the way you already work

Start with the outcome and scope. A good fit is clear about who it is for, what is covered, how implementation works, and what happens when the service detects a problem.

People also look for

Keep exploring EDR, MDR & RMM

Compare managed security options, understand pricing, and decide what level of endpoint oversight fits a smaller organization.