N-able Ships N-central 2026.4 HF3 With 17 Flaw Fixes
N-able's N-central 2026.4 Hotfix 3 patches 17 flaws and removes legacy APIs after 4EverAble2Shell exploitation. Agents and Probes must be upgraded too.

N-able released N-central 2026.4 Hotfix 3 (HF3), labelled a critical security update. It fixes 17 vulnerabilities and permanently removes the legacy API configuration option. The Hacker News reported it on November 17.
What changed. HF3 builds on HF2. N-able lists improvements to authentication and access control, Agent and Probe communications, file handling, server components, legacy APIs and user management. Remote control and Intune integration are currently blocked, per N-able’s notes as relayed by the outlet.
Exploitation context. Confirmed, per the same report: attackers are exploiting the earlier 4EverAble2Shell flaws to deploy cryptocurrency miners on vulnerable servers. Successful exploitation of 4EverAble2Shell depends on legacy API mode being enabled. Removing that mode in HF3 closes this vector. Our earlier coverage has the initial timeline.
Who must act. On-premise N-central servers need the upgrade. Hosted servers are patched automatically. N-able states that all customers, hosted and on-premise, must upgrade every Agent and Probe. Agents and Probes left on old versions are susceptible to impersonation.
The fixed flaws. The report lists 17 entries covering missing authentication on several server endpoints, a local privilege escalation in Patch Management, an appliance authentication bypass, XML external entity injection in two components, SSRF in report and export settings, and a path traversal that leads to remote code execution. We have not independently verified the CVE identifiers in that list, so none are cited here. Check N-able’s advisory for the authoritative IDs.
Researcher disclosure. Independent researcher Sean Bales, who disclosed the flaws, has published additional details for 24 CVEs. Bales states these are patched and should not work on the latest build. Confidence: single-outlet account of that statement.
Analysis: RMM platforms hold broad reach into managed endpoints, so the Agent and Probe upgrade requirement is not optional housekeeping. A patched server paired with stale Agents leaves the impersonation gap open.
More on threat intelligence.
Found this useful? Share it.


