N-able N-central Zero-Day Exploited Hours After Exploit Release
Attackers began compromising N-able N-central servers within hours of a public exploit. Researchers counted 21 hijacked systems, 19 of them fully patched to the latest update.
Attackers are already using a freshly published exploit against N-able's N-central platform, and most of the servers researchers found compromised were running the latest security update. The flaw, nicknamed "4EverAble2Shell", gives an unauthenticated attacker root access.
N-central is a remote monitoring and management tool. Managed service providers and IT teams run it to keep customers' machines and networks monitored, managed and protected without being on site. A hijacked server can therefore matter far beyond the machine itself.
Two exploits, two days after a patch
Security researcher Sean Bales released two zero-day exploits on November 12: 4EverAble2Shell and Agent2Shell. He says the first gives attackers root-level access to N-central appliances. The second targets the agent feature and, he claims, yields SYSTEM-level control of Windows machines.
The release came two days after N-able shipped emergency updates for earlier critical N-central zero-days that Bales had disclosed publicly that week. His proofs of concept were tested against appliance version 2026.4.1.26 HF2, the build released on November 10. Bales had published more than 30 alleged zero-days that week, after which N-able took its hosted N-central environments offline and told on-premises customers to power down their servers.
Bales has been openly critical of how N-able handles disclosures. He told the press that publishing his research and letting the vendor decide what to fix is easier for him. He says two unrelated remote code execution flaws in another N-able product, reported in July, remain unpatched.
How the attack works
4EverAble2Shell chains an Apache Axis flaw, CVE-2026-90436, with a separate privilege escalation weakness in N-central. The exploit works only if the Legacy API feature is switched on, and that feature is off by default.
Cybersecurity firm Previdian saw probing of its N-central honeypot at about 08:30 UTC on November 12, using the same Java class as the public exploit. Requests later turned into the full chain. Commands first run as the "nable" service account. The escalation step then abuses a privileged helper, using a symbolic link so that a script owned by root becomes writable, edits it, and triggers N-central's server control feature to run commands as root. The payload tried to fetch a shell script from an attacker-controlled server. Previdian tracks the escalation bug as VULN-2026-0009.
Twenty-one servers and a miner
Another firm, Huntback, saw the same attacker address probing its honeypots at the same time and starting full exploit attempts at 09:16 UTC. The attackers installed an XMRig Monero miner set to use about half of the CPU cores, which likely makes it harder to spot.
By 12:50 UTC, Huntback found 21 active miners, each having submitted mining shares within five minutes. All 21 addresses hosted N-central. Nineteen ran version 2026.4.1.26, the latest Hotfix 2 build. The servers sat in the United States, Canada, South Africa, the United Kingdom, Germany, France and Sweden.
N-able's own advisory said it had seen no sign of compromise through the new flaws. It is restricting some features and integrations, has disabled the Intune integration, and asks on-premises customers to confirm Legacy API access is off.
The attacks seen so far have been primarily cryptojacking, but compromised N-central infrastructure could be turned on managed customers. Because the exploit grants root, any server showing signs of it should be treated as fully breached. Huntback advises checking requests to /dms/services/ServerUI, unexpected xvd.service entries, mining processes, and files under /tmp/.xvd or /var/tmp/.xvd.
Source: BleepingComputer