N-able has shipped its third hotfix for the 2026.4 release of N-central, its remote monitoring and management (RMM) platform, in the space of about a week. RMM tools exist to give administrators remote, privileged reach into large numbers of client machines, which is also why attackers want them. N-central 2026.4 Hotfix 3 (build 2026.4.1.39) came out on Nov. 16, and the vendor calls it a "critical security update." It includes everything in Hotfix 2, adds a set of new authentication and validation fixes, and makes one significant change: the legacy API is gone. The configuration option for legacy APIs has been removed, and the legacy APIs are now permanently blocked.

The timing matters. In the days before the release, attackers were already getting into N-central servers through an exploit chain a researcher had disclosed, and planting cryptocurrency miners. Most of the infected servers counted so far were not unpatched stragglers. They were running Hotfix 2.

How we got here

The story began with a disclosure dispute. In early November, researcher Sean Bales posted what he said were 33 critical flaws in N-central under the name "Able2Shell," along with what he described as proof-of-concept material. Cybersecurity Dive reported that N-able released an emergency hotfix on a Tuesday (Hotfix 2) and briefly took hosted N-central offline. CEO John Pagliuca criticized the disclosure as uncoordinated and unverified. N-able also said that claims it had ignored responsible disclosure were inaccurate.

Bales then disclosed two more sets of flaws, which he called 4EverAble2Shell and Agent2Shell. According to The Hacker News, under specific conditions they allow code execution as root on the N-central server and SYSTEM-level access on Windows systems. Root and SYSTEM are the highest privilege levels on Linux and Windows respectively. Successful exploitation of 4EverAble2Shell hinges on the server's legacy API mode being enabled.

The entry point: an old SOAP library

The Hacker News reports that attacks on 4EverAble2Shell string together CVE-2026-90436, a flaw in Apache Axis rated CVSS 9.8, with a separate N-central privilege-escalation weakness to obtain root-level access. Axis 1.x is a retired Java framework for SOAP, an XML-based web service protocol. The National Vulnerability Database record, published Nov. 6, is marked "UNSUPPORTED WHEN ASSIGNED" and says Axis 1 is end-of-life, with no fixed Axis 1.x release expected.

NVD describes the bug this way. When Axis receives a SOAP fault (an error message) carrying an exception name in its details, it loads the named class and, if a string data element is also present, creates an object of that class before it checks whether the class is a legitimate fault type. An unauthenticated remote attacker can therefore make the server instantiate classes of their choosing. If a suitable class is on the application's classpath, that leads to remote code execution. NVD adds that the fault is parsed before any per-service handler chain runs, so authentication handlers configured on a service do not protect against it. Security people call this class of bug unsafe deserialization: trusting input that tells the program what kind of object to build.

When we checked, the NVD record's status was still "Awaiting Analysis." CVE-2026-90436 was also absent from CISA's Known Exploited Vulnerabilities (KEV) catalog version released Nov. 13. The catalog does already list a different N-able bug, CVE-2026-86218, which Cybersecurity Dive describes as a critical pre-authentication vulnerability patched in September; CISA added it on Sept. 8.

Miners on 21 servers, 19 of them patched

The cybersecurity company Huntback reported that attackers used the chain to install XMRig, a common Monero mining program, on 21 N-central servers, according to The Hacker News. The servers were concentrated in the US, South Africa, Canada, the UK, Germany, France and Sweden. The miner was designed to use only half of the available CPU cores, likely in an effort to avoid notice.

The most concerning detail is that 19 of the 21 servers were already running Hotfix 2. Huntback said applying Hotfix 2 is not enough on its own. N-able confirmed that threat actors are targeting customers who had not disabled the Legacy API. For its hosted environments, N-able said it had already turned the Legacy API off by default and turned Intune integration off. Huntback's guidance is direct: treat a hit as a full compromise, not a cleanup job.

That guidance makes sense even though the visible payload is "only" a miner. Huntback noted that the escalation hands the operator root on a host that manages customers' endpoints. A miner is the part of an intrusion that is easy to see. It does not tell you what else was done with that access.

What Hotfix 3 changes

The Hacker News lists 17 CVEs addressed in the new release, CVE-2026-129271 through CVE-2026-129287, matching N-able's release notes. They include:

  • A local privilege escalation in Patch Management.
  • An authentication bypass in the MMS3 appliance, caused by a predictable passcode.
  • A syslog injection in audit export that allows commands to run as root.
  • Several missing-authentication bugs, including in ServerMMS2, repositoryItemGet and the Take Control audit log.
  • XML external entity (XXE) flaws. In this class of bug, a crafted XML document makes the server read files or contact other systems.
  • A server-side request forgery (SSRF) flaw, where the server can be tricked into making requests on an attacker's behalf.
  • A path traversal in SIS GenericFiles that leads to remote code execution (CVE-2026-129286).

N-able's own release notes also describe the fixes by category:

  • Missing authentication and permission checks added to server operations.
  • Better authentication and session handling for Agents and Probes.
  • Extra validation on file publishing, file paths and XML import.
  • Hardening of inbound requests and outbound connections.
  • Improvements to user account management.
  • The legacy API configuration option removed and the legacy APIs permanently blocked.

Bales published additional details for 24 CVEs, The Hacker News reported, stating that these are patched vulnerabilities and "should not work on the latest patch." The Hacker News also reported that N-able noted remote control functionality and Intune integration were still blocked at the time of writing.

A note on tracking: NVD returned no record for the 17 new CVE IDs on Nov. 17. Vulnerability scanners and patch dashboards that depend on that feed may not flag them for a while, so don't wait for a scanner alert before upgrading.

What It Means for Defenders

Who is affected: N-central customers. Hosted customers will have their servers upgraded by N-able. On-premises customers have to upgrade themselves, and N-able says to do it as soon as possible. Managed service providers running self-hosted N-central are the most exposed group, particularly anyone who ever enabled the Legacy API.

What to patch:

  • Servers: Upgrade on-premises servers to N-central 2026.4 Hotfix 3, build 2026.4.1.39. It includes everything in Hotfix 2. Hotfix 2 is not enough on its own, because it was running on 19 of the 21 servers Huntback found infected.
  • Agents and Probes: Every customer, hosted ones included, must upgrade all Agents and Probes to 2026.4.1 HF3. N-able warns that Agents and Probes left on older versions are susceptible to impersonation. This is a separate rollout from the server upgrade, and it is easy to miss.
  • Device identity: Devices now depend on either the SMBIOS ID or the machine ID being available. If both are missing, N-central rejects the connection. Expect some machines to drop off after the upgrade. After Agents reconnect, review the new Inactive Assets tab (Configuration > Asset Discovery > Discovered Assets) for Agents that need attention, and don't assume they all went offline for harmless reasons.

What to check:

  • If your server ran with the Legacy API enabled at any point, treat it as possibly compromised. Huntback's advice is to treat a hit as a full compromise.
  • Check N-central servers for unexplained, steady CPU use, in particular a process holding about half the cores. That matches the miner behavior Huntback described.
  • Remember that a compromised RMM server can reach every endpoint it manages. If you find evidence of intrusion, extend the investigation to the managed estate. Agent2Shell, according to the researcher, can reach SYSTEM on Windows systems.
  • Monitor NVD and CISA KEV for the CVE-2026-129271 to CVE-2026-129287 range and for CVE-2026-90436. None of them were listed in KEV when we checked, and NVD had no record of the 17 new IDs.

What to rotate: None of the sources gives N-able-specific credential guidance. However, a full compromise of a root-level management server generally means rotating credentials stored on or used by that server, including N-central administrator accounts and any integration secrets. Make that decision as part of your incident response, using Huntback's full-compromise framing.

For CMMC and federal contractors: If N-central manages systems in your CUI enclave, an exploited RMM server is a potential incident to record and assess under your incident-response plan. That holds even if the visible payload was only a miner.

Sources