N-able Disables Legacy APIs to Block Active N-central Exploitation
Share
N-able has released a critical security update for its N-central remote monitoring and management (RMM) platform, addressing 17 zero-day vulnerabilities. The update includes a significant architectural change: the permanent removal of legacy APIs, which were being leveraged by attackers to compromise systems.
The vulnerabilities, tracked from CVE-2026-129271 to CVE-2026-129287, cover a broad range of security risks. These include remote code execution (RCE), privilege escalation, command execution, and authentication bypass flaws. The update, designated as N-central 2026.4 Hotfix 3, is designed to neutralise threats that have already been observed in the wild.
Blocking the 4EverAble2Shell Exploit Chain
The most pressing change in this release is the decommissioning of configuration options for legacy APIs. This move was necessitated by the discovery of an exploit chain known as “4EverAble2Shell”. Discovered by security researcher Sean Bales, the chain allows attackers to run shell scripts with root privileges on vulnerable N-central deployments.
The 4EverAble2Shell chain combines a critical bug in Apache Axis (CVE-2026-90436) with an N-central vulnerability that affects servers where legacy APIs remain enabled. Attackers began utilising public proof-of-concept code to deploy cryptocurrency miners within hours of the exploit’s public disclosure on 12 November.
While N-able has already applied the necessary patches to its hosted environments, the company is urging customers with on-premises deployments to upgrade their servers immediately. The vendor warned that failure to update Agents and Probes could leave systems susceptible to impersonation attacks.
Broadening Threats and System Hardening
The underlying Apache Axis vulnerability has also seen broader exploitation beyond RMM tools. Researchers have noted that threat actors are targeting Atlassian Confluence instances that have the “Remote API” setting enabled. Atlassian has since addressed the issue in Confluence version 9.2.28.
In addition to patching the 17 zero-days, the N-central Hotfix 3 introduces several security hardening measures. These include improvements to Agent verification, more robust inactive Agent management, and new device identification requirements for connections to the N-central environment. These changes aim to secure the communication between Agents, Probes, and the central management server.
Following the release of the patches, Sean Bales disclosed details of 24 additional vulnerabilities. However, these are reportedly addressed in the latest versions of N-central and should not pose a risk to organisations that have completed the upgrade to 2026.4 Hotfix 3 or later.




Leave a Reply