Overview
N-able has released N-central 2026.4 Hotfix 3, a critical security update addressing 17 vulnerabilities across its Remote Monitoring and Management (RMM) and Unified Endpoint Management (UEM) platform. The update follows the recent disclosure and active exploitation of earlier N-central vulnerabilities that attackers have used to gain elevated access and deploy cryptocurrency miners on vulnerable servers.
What Happened
The latest fixes address weaknesses involving authentication bypasses, missing authorisation checks, privilege escalation, file handling, XML external entity injection, SSRF, path traversal and remote code execution. N-able has also removed the legacy API configuration completely, closing the attack path used by the recently disclosed 4EverAble2Shell vulnerabilities. Some of the earlier flaws allowed attackers to execute code with root-level privileges on N-central servers or gain SYSTEM-level access to managed Windows systems.
Why MSPs Should Pay Attention
N-central is particularly sensitive because it provides centralised management of customer environments. A compromise of an RMM platform can potentially give an attacker a path from the MSP into multiple customer networks, making the platform itself a high-value target. The recent deployment of crypto miners demonstrates that attackers are already exploiting vulnerable N-central environments rather than simply waiting for theoretical opportunities.
What Administrators Should Do
On-premise N-central customers should upgrade their servers immediately, while hosted N-central customers receive the server-side fixes automatically. However, all customers must update their N-central Agents and Probes to the latest versions because outdated Agents and Probes remain vulnerable to impersonation. Administrators should also review systems for unexpected CPU usage, cryptocurrency-mining processes, suspicious accounts, unusual remote commands and unexplained changes to N-central configuration.
Expert in the Cloud Insight
RMM platforms should be treated as Tier-0 infrastructure. They are not simply another management application because a compromised RMM server, Agent or technician account can provide a direct route into multiple endpoints and customer environments. For MSPs, security should therefore include strict MFA, least-privilege administration, network isolation, rapid patching, monitoring of RMM activity and separate administrative access for the management platform itself. When attackers begin using an RMM vulnerability to deploy crypto miners, the bigger concern is not the mining — it is what they could do with the same access next.
Expert in the Cloud – The Future Is Now.
Leave a Reply