N-able ships N-central 2026.4 Hotfix 3 with 17 fixes while miners hit unpatched servers
N-able released N-central 2026.4 Hotfix 3 (build 2026.4.1.39) on 16 November 2026 and labelled it a critical security update. It fixes 17 vulnerabilities, CVE-2026-129271 through CVE-2026-129287, and permanently shuts off the Legacy API. That second change matters most right now. An attack chain that depends on the Legacy API has been used since 12 November to plant cryptocurrency miners on N-central servers, including servers that already had Hotfix 2.
What happened
N-central is N-able's remote monitoring and management platform. MSPs and IT teams use it to run scripts and push patches across thousands of endpoints. A bug in a tool like that is close to a bug in every machine it manages.
The trouble started on 9 November, when a batch of N-central vulnerabilities was published without coordinated disclosure. N-able took its hosted servers offline and told on-premises customers to do the same. Hotfix 2 followed on 10 November and closed the internet-facing, unauthenticated issues.
On 12 November a second set went public, covering abuse of the Legacy API and impersonation of N-central agents. A working proof of concept came with it. Within hours at least 21 N-central servers were running the XMRig Monero miner. Nineteen of them were on build 2026.4.1.26, which is Hotfix 2.
Hotfix 3 is N-able's answer to that second wave.
How the attack works
The chain behind the miners has two steps. The first is CVE-2026-90436, an unsafe reflection flaw in Apache Axis 1.x, the old SOAP library that N-central exposes through its Legacy API. Apache published it on 6 November. The 1.x branch is end of life, and every version up to 1.4 is listed as affected. It gives an unauthenticated attacker command execution as the N-central service account.
The second step is a local privilege escalation on the appliance that turns that foothold into root. The Legacy API is off by default, so servers where an admin had switched it on were the ones at risk.
The miner was tuned to stay quiet, using roughly half of the available CPU cores. On a busy RMM server that could go unnoticed for a long time.
A related agent-side issue was published at the same time. N-able says an attacker with a foothold on an endpoint could impersonate an agent, receive its task and script data, and report false status and metrics. Public claims that the agent issue also gives SYSTEM-level access on Windows devices have not been confirmed by N-able.
What Hotfix 3 fixes
The full list is in N-able's Hotfix 3 release notes. Using N-able's own CVSS 4.0 scores, three are critical, eight are high and six are medium. The three critical ones:
- CVE-2026-129272 (9.3): authentication bypass on the MMS3 appliance interface through a predictable passcode.
- CVE-2026-129280 (9.3): ServerUI SOAP operations missing authentication and authorisation checks, allowing access to and changes in other customers' data.
- CVE-2026-129286 (9.2): path traversal in software update metadata that lets an attacker write files and run code as the N-central service account.
Other notable fixes include root command execution through the Audit Export syslog settings (CVE-2026-129273), a sendmail argument injection in the test email feature (CVE-2026-129282), two XML external entity bugs and an SSRF. N-able has not said that any of the 17 have been exploited.
The update has trade-offs. Remote control other than Take Control is disabled in this build, and the Intune integration stays blocked. N-able says both will return in the next release. A further release will cover remaining data-leakage issues that need privileged access.
Who is affected
- On-premises N-central below 2026.4.1.39. You must upgrade the server yourself. Direct upgrades are supported from 2025.4, 2026.1, 2026.2, 2026.3 (any hotfix) and 2026.4 up to Hotfix 2. Older builds need an intermediate step.
- Hosted N-central. N-able is applying Hotfix 3 to the servers, so no server work is needed.
- Every customer's Agents and Probes, hosted or not. They must be upgraded to 2026.4.1 HF3. N-able warns that agents and probes left behind are open to impersonation.
What to do now
- Upgrade on-premises servers to 2026.4.1.39 as an emergency change. Do not wait for a maintenance window.
- Push the HF3 Agent and Probe upgrades to every device, then give agents time to reconnect and review the new Inactive Assets tab. Devices without an SMBIOS ID or machine ID will now be rejected.
- If your server ever had the Legacy API turned on, assume it may have been compromised. Look for
xvd.serviceunits, files under/tmp/.xvdor/var/tmp/.xvd, cron entries you did not create, sustained CPU load, and requests to/dms/services/ServerUIreferencingjline.internal.TerminalLineSettings. A confirmed hit means rebuilding the server and rotating every credential it held, not just removing the miner. - Keep the N-central console off the open internet where you can, and limit access to known admin networks.
Most of the 21 hijacked servers were patched to the latest build available that week. They were exposed because of a setting. Our Attack Surface Management service watches for exactly that: internet-facing management consoles, the versions they run and the endpoints they expose, so a forgotten option is found before someone else finds it.
