Threat actors have begun exploiting a critical zero-day vulnerability in N-able N-central, officially dubbed 4EverAble2Shell, mere hours after a publicly released proof-of-concept was made available.
This severe flaw allows unauthenticated attackers to achieve remote code execution (RCE) with root privileges on vulnerable N-central servers, even those running the latest patches. The exploitation chain leverages a recent Apache Axis vulnerability, which carries a CVSS score of 9.8, combined with an unspecified security hole present in deployments that have the Legacy API functionality enabled.
Security researcher Sean Bales previously released details regarding this zero-day on GitHub, which occurred two days before threat actors started exploiting the vulnerability. This rapid transition from disclosure to active exploitation highlights the immediate danger posed by the flaw to organizations using the platform.
The attack methodology involves chaining the exploit targeting the Apache Axis bug to first achieve Remote Code Execution, followed by an attempt to elevate privileges to root and execute a shell script on the target server.
N-able reacted immediately to the emergence of these zero-days by restricting several N-central features and integrations, specifically targeting the Legacy API and Intune integration functionality to mitigate the risk.
The exploit chain has been observed against N-central servers that were updated to version 2026.4 HF2, which carries build number 2026.4.1.26 and supposedly includes fixes for previously disclosed Able2Shell zero-days.
The technical requirement for this exploit to function is that the platform’s Legacy API functionality must be enabled on the affected N-central deployment, making configuration a key factor in potential exposure.
Sources: