The short version
- The flaw. A researcher released a working exploit, 4EverAble2Shell, that lets unauthenticated attackers run commands as root on N-able N-central servers that have the Legacy API enabled. It chains an Apache Axis bug, CVE-2026-90436, with a separate N-central privilege-escalation weakness.
- Exploitation. Attackers began probing within hours and compromised servers to install an XMRig Monero miner. Huntback and Lupovis counted 21 hosted N-central installations mining, 19 of them running the latest N-able hotfix.
- Vendor response. N-able restricted features and integrations, disabled its Intune integration and said on 12 November it had seen no signs of compromise from the new flaws. On 13 November it said it had identified additional indicators of compromise and was working with specific customers.
- Second exploit. The researcher, Sean Bales, also published Agent2Shell, which he says yields SYSTEM privileges on Windows machines through N-central's agent. Neither source reports it being used in attacks.
Timeline
| Date | Event |
|---|---|
| 10 Nov | N-able releases Hotfix 2, build 2026.4.1.26, for N-central, addressing zero-days Bales had published at the weekend. |
| 12 Nov | Bales publishes proof-of-concept exploits for 4EverAble2Shell and Agent2Shell on GitHub. |
| 12 Nov, 08:30 UTC | Previdian and Huntback record requests to their N-central honeypots; Previdian's requests used the same Java class as the public exploit. |
| 12 Nov, 09:16 UTC | Huntback sees the first attempts to run the complete exploit chain. |
| 12 Nov | N-able issues an advisory restricting certain N-central features and integrations, including disabling the Intune integration. |
| 12 Nov, 12:50 UTC | Huntback counts 21 active miners tied to compromised N-central servers. |
| 13 Nov | N-able says it has identified additional indicators of compromise and is working closely with the affected customers. |
The flaw and the attack chain
The flaw, named 4EverAble2Shell by researcher Sean Bales, lets unauthenticated attackers run commands as root on N-central, the remote monitoring and management (RMM) platform that managed service providers use to administer customer devices. Exploitation requires the platform's Legacy API to be enabled; N-able says that is already the default. Bales's chain uses Apache Axis CVE-2026-90436, rated 9.8, to run commands as the 'nable' service account, then a separate privilege-escalation weakness to reach root.
Previdian tracks the escalation step as VULN-2026-0009 and has added it to its own known-exploited catalogue. It says the step abuses N-central's setLDFileOwner helper and a symbolic link to make a root-owned script writable; the attacker then alters the script and calls serverControl to execute commands as root, attempting to restore the files afterwards. Bales says the chain works against N-central 2026.4 HF2, build 2026.4.1.26, issued on 10 November.
Bales also released Agent2Shell, which he says reaches SYSTEM privileges on Windows machines through N-central's agent component. Neither source reports it being used in attacks. N-able says it is restricting certain N-central features and integrations while it develops further fixes.
Exploitation and payload
Previdian told BleepingComputer it saw requests against its N-central honeypot at about 08:30 UTC on 12 November, using the same Java class as the published exploit, and later confirmed attempts to run the full chain. Huntback saw the same attacker address and recorded full-chain attempts from 09:16 UTC. The payload attempted to download and execute a shell script from 157.20.241[.]16 while sending diagnostic data and command output back to that address.
The script installed an XMRig Monero miner, which uses a victim's processors to mine cryptocurrency for the operator. Huntback says the miner was limited to about half the available CPU cores, likely to make it harder to detect, and that infected hosts were registered under identifiers of 'nc_' followed by their IP address. Lupovis reported systemd or cron persistence.
At 12:50 UTC on 12 November, Huntback counted 21 miners that had submitted shares in the previous five minutes; checking the addresses confirmed all 21 were hosted N-central installations, 19 of them on the latest hotfix. Lupovis reported the same 21 rigs, in the US (9), South Africa (4), Canada (4), the UK, Germany, France and Sweden. "Our decoys never execute anything, so none of the listed rigs are ours," Lupovis told SecurityWeek.
Response and exposure
N-able took its hosted N-central environments offline earlier in the week and urged on-premises customers to shut down servers after Bales published more than 30 alleged zero-days. On 12 November it said it had disabled the Intune integration, was restricting other features as a precaution, and had seen no signs of compromise from the new flaws. The protections were applied to hosted environments, and customers were told to keep upgrading agents and probes under earlier hotfix guidance.
On 13 November N-able said its investigation had turned up additional indicators of compromise and that it was working closely with the specific customers involved. By then, Lupovis and Huntback had reported successful exploitation against production N-central servers.
The exposure falls on MSPs and internal IT teams running N-central, because root on the management server can reach the customer devices and networks it controls. Huntback's write-up says a hit should be treated as a full compromise rather than a cleanup job. Bales has criticised N-able's handling of his reports, saying two unrelated remote code execution flaws in a different N-able product, disclosed in July, remain unpatched.
What is not known yet
- Who is operating the campaign, and whether one actor is behind all 21 mining infections.
- Whether attackers used root on the management servers to reach managed customer endpoints or take data from them.
- How many N-central servers are exposed or were compromised beyond the 21 seen mining.
- Whether Agent2Shell has been exploited anywhere in the wild.
- When N-able will patch the privilege-escalation weakness that the public chain relies on.
What to do
If you run N-central
- Check that Legacy API access is disabled and leave the Intune integration off while N-able's restrictions apply.
- Apply Hotfix 2, build 2026.4.1.26, and keep upgrading agents and probes as N-able issues further fixes.
- Search logs for requests to /dms/services/ServerUI, particularly ones referencing jline.internal.T, and block traffic to 157.20.241[.]16.
- Hunt for miner processes named after the host IP, XMRig binaries, and systemd or cron entries; if found, rebuild the server, rotate its credentials and review the customer environments it manages.
If an MSP manages your systems
- Ask whether their N-central servers had Legacy API enabled and whether they found miner activity or the listed indicators.
- Ask what they have checked on your own endpoints and what they will do if their management server is confirmed compromised.
For everyone else
- Treat internet-facing management platforms as high-value targets: turn off optional APIs and integrations you do not use, such as legacy interfaces, so that a single patched flaw does not hand over administrative control.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.