N-central Hotfix 3 is out: N-able has released version 2026.4 Hotfix 3 (build 2026.4.1.39) of N-central, its remote monitoring and endpoint management platform, and classifies it as a critical security update. The release notes, published on 16 November 2026, list 17 fixed vulnerabilities. The update arrives a few days after attackers exploited a previously disclosed flaw chain to install cryptocurrency miners on N-central servers.
What N-central Hotfix 3 fixes
According to N-able’s release notes, Hotfix 3 builds on Hotfix 2 and includes all of its changes. New are improvements in six areas:
- Authentication and access control: missing authentication and permission checks added to further server operations.
- Agent and Probe security: changes to how Agents and Probes authenticate with the server, including session handling.
- File and import handling: additional validation for file publishing, file paths and XML imports.
- Server hardening: changes to how the server handles incoming requests and makes outbound connections.
- Legacy APIs: the configuration option has been removed and the old interfaces are now permanently blocked.
- User management: improvements to how user accounts are managed and secured.
The 17 CVEs are numbered CVE-2026-129271 to CVE-2026-129287. According to N-able, they include a local privilege escalation in patch management (CVE-2026-129271), an authentication bypass via a predictable MMS3 appliance passcode (CVE-2026-129272), a syslog injection in audit export that allows root command execution (CVE-2026-129273), several missing authentication checks in ServerMMS components, an SSRF flaw in the report and data export settings (CVE-2026-129284) and a path traversal flaw in SIS GenericFiles that leads to remote code execution (CVE-2026-129286). There are also two XML external entity flaws (CVE-2026-129283 and CVE-2026-129287). N-able does not give CVSS scores in the release notes.
Background: Able2Shell, 4EverAble2Shell and Agent2Shell
Hotfix 3 is the second security update within a week. On 10 November, N-able released Hotfix 2 (build 2026.4.1.26) to fix a set of flaws that independent security researcher Sean Bales had disclosed under the name Able2Shell. Shortly afterwards, according to The Hacker News, Bales published two more sets, 4EverAble2Shell and Agent2Shell, whose proof-of-concept exploits also worked against Hotfix 2.
4EverAble2Shell reportedly enables unauthenticated remote code execution as root on N-central servers. It requires the Legacy API to be enabled and reachable from the internet. N-able stresses that this interface is off by default and not recommended. Agent2Shell, according to Bales, uses more than ten zero-day flaws to run commands as NT AUTHORITY\SYSTEM on managed Windows machines – provided the attacker knows the target appliance ID.
N-able’s release notes do not say whether, or which of, the 17 fixed CVEs correspond to these chains. With the Legacy APIs now permanently blocked, however, the precondition for 4EverAble2Shell is gone.
Attacks with crypto miners
The flaws did not remain theoretical. According to The Hacker News, citing the security firms Previdian and Huntback, attackers combined a critical flaw in the bundled Apache Axis component (CVE-2026-90436, CVSS 9.8) with an N-central privilege escalation to obtain root access, then downloaded a shell script.
Huntback says the group installed the XMRig Monero miner on 21 N-central servers in countries including the US, South Africa, Canada, the UK, Germany, France and Sweden. The miner used only half of the available CPU cores, likely to attract less attention. 19 of the affected servers were already running Hotfix 2. Huntback warns that a hit should be treated as a full compromise, not a clean-up job, because the attacker has root on a host that manages customers’ endpoints. According to The Hacker News, N-able confirmed that attackers are targeting customers who had not disabled the Legacy API and shared indicators of compromise, including the IP address 157.20.241[.]16.
What administrators should do now
N-central is widely used by managed service providers to run their customers’ IT. A compromised instance can therefore put many downstream networks at risk. Flaws in other central tools are similarly sensitive, such as the root access flaw in the Dokploy deployment platform or the login bypass in Apache Shiro.
- Update the server: N-able says on-premise customers should upgrade to 2026.4.1.39 as soon as possible. Direct upgrades are supported from version 2025.4 onwards. N-able upgrades hosted instances itself.
- Update Agents and Probes: this explicitly applies to all customers, including hosted ones. According to N-able, Agents and Probes that are not upgraded are susceptible to impersonation.
- Review inactive Agents: the new “Inactive Assets” tab under Configuration > Asset Discovery > Discovered Assets lists Agents that N-central has made inactive. Devices must now provide an SMBIOS ID or machine ID, otherwise the server rejects the connection.
- Check for compromise: anyone who ever enabled the Legacy API should check logs and outbound connections against the published indicators and treat an infection as a full breach.
Agents showing up as inactive after the update is not automatically a red flag. N-able lists typical reasons: cloned virtual machines, re-imaged computers, Agents installed twice, a server restored from backup, or Agents that were offline longer than their token remained valid. The tab only fills as Agents reconnect after the upgrade. “Set Active” reactivates an Agent, and all actions are logged. The distinction from Hotfix 2 matters: that release changed communication between Agents and Probes, while Hotfix 3 concerns the connection from Agents and Probes to the server.
Some restrictions remain for now: remote control functions other than Take Control are disabled, and the Intune integration is blocked. N-able had already restricted both areas as a precaution on 13 November.
Analysis
The case shows how quickly public proof-of-concept exploits now turn into real attacks. According to Previdian, the first targeted probing was observed within hours of publication. Tools that analyse patches automatically speed this up further, as the report on the AI tool exploit_agent shows. For operators of central management platforms, that means applying hotfixes promptly, permanently disabling interfaces they do not need and not exposing the management interface to the internet unprotected. Bales has since published details on 24 CVEs and says these are patched and should not work against the current version.




