N-able Fixes 17 Critical N-central Flaws After Crypto Miner Attacks

N-able has rolled out a major security update—Hotfix 3 for N-central version 2026.4—to neutralize 17 vulnerabilities that were under active exploitation in Remote Monitoring and Management (RMM) and Unified Endpoint Management (UEM) tools. These flaws, many enabling privilege escalation, credential bypass, and remote code execution, were reportedly leveraged by attackers to install crypto miners via earlier bugs. The update strengthens authentication, access control, file handling, server hardening, agent security, and has removed support for legacy APIs entirely.

What Went Wrong: Exploits & Vulnerabilities

Recent attacks stemmed from a cluster of previously disclosed bugs known as 4EverAble2Shell and Agent2Shell. These bugs let malicious actors execute arbitrary code as root and gain SYSTEM-level access on Windows when the legacy API mode was active. Now that the legacy API has been removed in the 2026.4 Hotfix 3 release, that particular attack route is closed.

Some of the more severe issues patched include a local privilege escalation flaw, authentication bypass via predictable passcodes, root-command execution through syslog injection, missing authorization checks in SOAP operations, server-side request forgery (SSRF), and remote code execution via path traversal and XML external entity (XXE) injection. In total, 17 CVEs were addressed, ranging from CVE-2026-129271 through CVE-2026-129287.

What Users Must Do

On-premises customers are urged to upgrade their servers immediately to ensure protection. For hosted deployments, the server‐side fixes are already being applied automatically. However, both on-prem and hosted users need to update all Agents and Probes to the latest versions; unpatched ones can still be impersonated by attackers.

Critical controls have also been tightened around authentication and access control, Agent/Probe communication, file import handling, user management, and other traditional weak spots. Export-import and server components have been hardened, user enumeration flaws fixed, and mechanisms to forge or tamper with audit logs and configuration settings have been sealed.

The vulnerabilities in question were revealed and tracked by independent researchers, who provided details on over two dozen CVEs. The recent update states that the patched systems should no longer be vulnerable to threats flowing from those issues.

In short: N-able has issued a sweeping update to close major threats that attackers were actively abusing. Customers running N-central should treat this as non-optional.

Analytical insight: This incident illustrates how legacy APIs and insufficient access controls remain among the most dangerous attack surfaces in enterprise tools. Rapid patching matters, but so does pushing out complementary measures—complete removal of vulnerable modes (like the legacy API), stricter authorization, and validation everywhere. Moving forward, N-able users should verify that all software components—including Agents and Probes—are kept up to date, and monitor for indicators of compromise tied to these CVEs.