Live coverage: Netherlands Phase Black, global cyberattacks & preparednessLast checked: Tuesday 17 November 2026, about 14:00 PKT
Home › N-able N-central Able2Shell: Hotfix 3 After Miners Hit Patched Servers
Global Cyber Preparedness News

N-able N-central Able2Shell: Hotfix 3 After Miners Hit Patched Servers

N-able has released a third emergency hotfix for its N-central platform, fixing 17 vulnerabilities and permanently removing the Legacy APIs that attackers used to break in. The release, on 16 November 2026, comes a week after a researcher published proof-of-concept code for 33 alleged N-central flaws — and four days after attackers used a new exploit chain against the previous hotfix to install cryptocurrency miners on 21 live servers, 19 of which were already running the patch. N-central is the remote monitoring software that managed IT providers use to run their clients' computers, so a flaw in it is a supply-chain flaw: one compromised server can reach hundreds of client machines. This page sets out the verified timeline, what Hotfix 3 fixes, and what providers must still do.

In short

Attribution: The flaws were disclosed by independent researcher Sean Bales; the miners were installed by an unidentified operator. N-able released N-central 2026.4 Hotfix 3, build 2026.4.1.39, on 16 November 2026 — a critical security update fixing 17 vulnerabilities, tracked as CVE-2026-129271 through CVE-2026-129287, including privilege escalation, authentication bypass, root command execution through audit log exports, remote code execution through path traversal, and XML external entity injection. The update permanently removes the Legacy API configuration option, blocking those APIs for good, and N-able warns that all Agents and Probes must also be updated to the latest version — unupgraded components remain susceptible to impersonation. The release follows the Able2Shell disclosure of 9 November 2026, in which Bales published proof-of-concept code for 33 alleged N-central flaws, and the 4EverAble2Shell exploit chain of 11-12 November 2026, which attackers used within about five hours to install Monero miners on 21 live N-central servers — 19 of them already running Hotfix 2. Whether the 17 flaws fixed by Hotfix 3 are the same bugs used in the miner attacks has not been established by the public information.

What happened: Hotfix 3, 17 flaws, Legacy APIs gone

N-able has released N-central 2026.4 Hotfix 3, which it describes as a critical security update for its Remote Monitoring and Management and Unified Endpoint Management platform. The update was published on N-able's status site on 16 November 2026, as build 2026.4.1.39. It fixes 17 vulnerabilities, tracked as CVE-2026-129271 through CVE-2026-129287, and it builds on the protections delivered in Hotfix 2, adding improvements across authentication and access controls, Agent and Probe communications, file handling, server components, legacy APIs and user management. The most consequential change is the complete removal of the Legacy API configuration option: the legacy APIs are now permanently blocked, with no way to turn them back on. That matters because the Legacy API was the route the attackers used. N-able also warns that installing the server update alone is not enough: all customers, hosted and on-premises, must upgrade all of their Agents and Probes to the latest version to be fully protected, because unupgraded components remain susceptible to impersonation. At the time of writing, remote control functionality and Microsoft Intune integration are blocked.

The 17 flaws in brief

The 17 vulnerabilities addressed in Hotfix 3 span the platform. They include a local privilege escalation in Patch Management (CVE-2026-129271), an authentication bypass on the MMS3 appliance through a predictable passcode (CVE-2026-129272), root-level command execution through audit export syslog injection (CVE-2026-129273), and, at the other end of the range, an XML external entity injection in the SIS repository parser (CVE-2026-129287). Between them are remote code execution through a path traversal flaw, server-side request forgery, and several missing authentication and authorisation checks, including in SOAP operations. N-able has not published severity scores for the 17 flaws, and the release notes do not mention active exploitation. The researcher who disclosed the original flaws, Sean Bales, has published additional technical details for 24 CVEs and has said the vulnerabilities he detailed should not work against the latest patched release. The 17 CVEs in Hotfix 3 and the researcher's 24 CVEs are not the same list, and this page does not treat them as identical.

Able2Shell: how it started

The story began on 9 November 2026, when independent security researcher Sean Bales, operating under the GitHub account Oracle-Security — since renamed MSPNightmare — published proof-of-concept code for 33 alleged vulnerabilities in N-able N-central, under the name Able2Shell. The earliest commit is dated 9 November 2026 at 04:14 UTC. Bales said one attack chain lets an unauthenticated attacker run commands on the server, and the 33 flaws chain into four exploit paths — three remote code executions and one root escalation. The code was published without prior notice to the vendor, and N-able has said the research was not responsibly disclosed through its established reporting channels. N-able took its hosted N-central environments offline and told customers running their own N-central servers to take them offline until further notice. On 10 November 2026, N-able released N-central 2026.4 Hotfix 2, build 2026.4.1.26, fixing seven CVEs, and brought hosted servers back online. Tenable's FAQ on the incident notes that N-able has published seven CVEs and a hotfix, but has not mapped its CVEs to the researcher's 33 findings or commented on them individually.

4EverAble2Shell and Agent2Shell: the exploits that beat the hotfix

Late on 11 November and into 12 November 2026, Bales published two more exploit sets, 4EverAble2Shell and Agent2Shell, which he said worked against Hotfix 2. 4EverAble2Shell chains CVE-2026-90436 — a flaw rated 9.8 out of 10 in the bundled, end-of-life Apache Axis 1.x SOAP engine — with an N-central local privilege escalation that has no CVE yet, producing unauthenticated remote code execution as root on the N-central server. It requires the Legacy API to be enabled and reachable from the internet. Agent2Shell covers more than ten flaws leading to SYSTEM privileges on managed Windows endpoints — the client machines a provider manages through N-central. On 12 November 2026, N-able said it was investigating the new claims. The speed of what followed is the point of this story: attackers were attempting the full exploit chain within about five hours of the new code appearing, and by the afternoon of 12 November a public mining pool listed 21 compromised N-central servers.

The miners: 21 servers, most already patched

On 12 November 2026, security firm Huntback reported that a newer exploit chain, 4EverAble2Shell, was used to install cryptocurrency miners on 21 live N-central servers it identified. At 12:50 UTC, a public mining pool's per-rig list showed 21 rigs whose names begin nc_ — the installer names each rig after the victim server — each having submitted a share in the preceding five minutes, at a combined hashrate of roughly 25 kH/s. Huntback sent ordinary web requests to each of the 21 addresses: all 21 served N-central's web interface, and 19 reported build 2026.4.1.26 — Hotfix 2. One host was on 2025.3.1.9. As Huntback put it, applying Hotfix 2 was not enough on its own: 19 of the victims were already running it. The payload was XMRig, a miner for the privacy-focused cryptocurrency Monero, configured to use about half of each server's CPU cores so it would go unnoticed. After escalating, the attackers downloaded a script named jup.sh from 157.20.241[.]16, installed XMRig under a hidden .xvd folder, and added systemd and cron persistence with a watchdog. The same wallet also ran miners on other exploited platforms, including Jpom, FreePBX, MLflow and PaperCut. The servers were in seven countries, most of them in the United States. So far the only observed payload is a Monero miner — but the attack gives full root control, so a miner may not be the only thing installed, and every affected server needs a full investigation, not just a cleanup.

What N-able says — and what it has not said

N-able's public statements have been careful, and they are worth reading as written. On 11 November 2026, the company said it was observing scanning activity associated with the publicly released proof-of-concept code, but had seen no indications of compromise within N-central hosted servers. That statement is scoped to the servers N-able hosts itself — it says nothing about customer-run servers, which is where the miners were found. N-able has said the server attack only works when the non-default Legacy API is turned on and reachable from the internet, and that hosted N-central is not affected. It has also said that every flaw exploitable without authentication has been addressed, and that the remaining vulnerabilities require an authenticated N-central account, often with elevated privileges. What N-able has not done: it has not mapped its CVEs to the researcher's 33 findings; it has not said whether the 17 flaws fixed by Hotfix 3 are the bugs used in the miner attacks; and the Hotfix 3 release notes do not mention active exploitation or give severity scores for the 17 flaws. Huntress, reporting N-able's position, said the company had no evidence that any customer environment had been successfully exploited — a statement made before Huntback's report of the 21 mining servers.

What is still unknown — DEVELOPING as of Tuesday 17 November 2026

Three things are not yet settled. First, whether the 17 vulnerabilities fixed by Hotfix 3 are the same bugs used in the miner attacks: the public information does not establish that, and the two lists — N-able's 17 CVEs and the researcher's 24 — are not the same. Second, the full scope of the compromise: 21 servers were counted in a public mining pool, but that counts only servers mining visibly, and root access means other activity on those servers cannot be ruled out. Third, whether Agent2Shell was used against managed endpoints: the chain targets SYSTEM privileges on client machines, and no public report has yet confirmed or ruled out endpoint compromise. What is known is the fix: Hotfix 3, build 2026.4.1.39, with all Agents and Probes updated, and the Legacy APIs permanently removed. Providers running N-central on-premises should treat the update as urgent, check for the miner indicators — the jup.sh script, the hidden .xvd folder, unexpected systemd and cron entries, and connections to 157.20.241[.]16 — and check N-able's status page for anything newer. Last checked Tuesday 17 November 2026, about 15:15 PKT.

Frequently asked questions

N-central is N-able's Remote Monitoring and Management (RMM) and Unified Endpoint Management (UEM) platform. Managed IT service providers use it to oversee and control their clients' computers — patching, monitoring and remote access — from one server. That is why a flaw in N-central is a supply-chain risk: one compromised server can reach many client machines.

Able2Shell is the name independent researcher Sean Bales gave to a set of 33 alleged vulnerabilities in N-able N-central, published with proof-of-concept code on 9 November 2026. Bales said the flaws chain into four exploit paths — three remote code executions and one root escalation — and that one chain lets an unauthenticated attacker run commands on the server.

A second exploit chain Bales published late on 11 November 2026, which he said worked against Hotfix 2. It chains CVE-2026-90436 — a flaw rated 9.8 in the bundled, end-of-life Apache Axis 1.x SOAP engine — with a local privilege escalation, giving unauthenticated remote code execution as root. It needs the Legacy API enabled and reachable from the internet. Attackers used it within about five hours to install crypto miners.

N-central 2026.4 Hotfix 3, build 2026.4.1.39, released 16 November 2026, fixes 17 vulnerabilities tracked as CVE-2026-129271 through CVE-2026-129287 — including privilege escalation, authentication bypass, root command execution through audit log exports, remote code execution through path traversal, and XML external entity injection. It also permanently removes the Legacy API configuration option. N-able published no severity scores for the 17 flaws.

Install N-central 2026.4 Hotfix 3, build 2026.4.1.39, and then update every Agent and Probe to the latest version — N-able warns that unupgraded components remain susceptible to impersonation. Check that the Legacy API is gone, and check your server for miner indicators: the jup.sh script, a hidden .xvd folder, unexpected systemd and cron entries, and connections to 157.20.241[.]16. If you find any of them, treat the server as compromised and investigate fully.

N-able says hosted N-central is not affected by the server attack, and that it has seen no indications of compromise within the servers it hosts. Even so, N-able says all customers, hosted and on-premises, must upgrade all of their Agents and Probes to the latest version to be fully protected.

Miners are the only payload observed so far — XMRig, mining Monero at about half of each server's CPU cores. But the attack gives full root control of the server, so a miner may not be the only thing installed. Every affected server needs a full investigation, not just removal of the miner.

Hotfix 3 is the current fix, and the researcher has said the vulnerabilities he detailed should not work against the latest patched release. But the fix only works if it is fully applied — server, Agents and Probes — and whether every one of the 33 originally reported flaws is covered has not been confirmed. Keep watching N-able's status page for a follow-up hotfix.

Sources & check time. The Hacker News, 'N-able Patches 17 N-central Flaws as Attackers Exploit Earlier Bugs to Deploy Crypto Miners' (17 Nov 2026); Tenable, 'Able2Shell FAQ: N-able N-central Zero-Days and Hotfix 2' (11-12 Nov 2026); N-able status page and release notes, via The Hacker News and DaySec (16-17 Nov 2026); Huntback, via Tenable and severitydaily (12 Nov 2026); BleepingComputer, via reporting (12 Nov 2026). Last checked Tue 17 Nov 2026, about 15:15 PKT.
Figures are given with their snapshot time and source. Developing items are marked as developing. Last checked Tuesday 17 November 2026, about 14:00 PKT.