1-minute read
What a defender needs to know
N-able released N-central Hotfix 2 build 2026.3.1.10 on August 6 and says self-hosted operators must install it even if they already applied Hotfix 1. The release supersedes build 2026.3.1.7 with additional hardening for CVE-2026-18577. N-able and Huntress report active exploitation against the RMM control plane used by MSPs to administer downstream customer endpoints.
Attackers used N-central’s Take Control function to reach managed Windows systems. Huntress observed strategic targeting of key servers, process-list reconnaissance, and rapid movement across downstream hosts. N-able identifies a Cloudflared service and svchost.exe in users’ Documents folders as investigation pivots. Installing the server hotfix blocks the documented console path but does not remove services, tools, accounts, or jobs already placed on managed endpoints.
Confirm every self-hosted N-central server runs Hotfix 2 build 2026.3.1.10; N-able says mitigations have already been applied to hosted instances. Huntress’s later August 3 measurement found 13.6% of its reachable cohort still unpatched overall and 28.6% of reachable self-hosted servers unpatched. Correlate ui_access_control.log, Windows Application event IDs 4102, 8192, and 8193, firewall and identity records, and endpoint logs under C:\ProgramData\GetSupportService_N-Central\Logs\. A published IP or Take Control log alone is not proof of compromise because several IPs are VPN exits and the logs also appear during legitimate support.
Verify Hotfix 2 or the hosted mitigations, reconcile all console access and automation, map every unexplained remote session to a downstream endpoint, remove persistence, and monitor for unexplained tunnel or Take Control activity through a defined period. Missing console or endpoint records leave the scope unresolved.