N-able N-central is software that IT service providers and managed service teams use to monitor and manage customer devices. An on-premises N-central server is a central point of control, so compromising it can give an attacker a route into many managed systems.
On 11 and 12 November 2026, independent researcher Sean Bales published a proof-of-concept exploit for 4EverAble2Shell. Attackers began using it within hours. Researchers at Huntback traced the activity to one operator and reported 21 compromised N-central servers, 19 of them running Hotfix 2 (build 2026.4.1.26). No named threat actor has been linked to the campaign as of 12 November.
Item | Details |
|---|---|
Product | N-able N-central, on-premises deployments |
Entry point | CVE-2026-90436, a flaw in the Apache Axis component bundled with N-central (CVSS 9.8) |
Second stage | A separate N-central flaw that appears when the Legacy API is enabled |
Result | Unauthenticated remote code execution as root on the server |
Observed payload | XMRig Monero cryptocurrency miner, installed by a shell script named jup.sh |
Exploitation status | Exploited in the wild from 12 November 2026 |
Hosted N-central | Not affected by the server chain, according to SOCRadar's reading of N-able's advisory |
The exploit chain works through a weakness in how Apache Axis handles SOAP fault messages. A crafted request can steer the software into processing malicious input, which leads to command execution. The researcher reports that the chain requires the Legacy API to be enabled.
A companion set of exploits, which the researcher calls Agent2Shell, targets managed Windows agents and can reach SYSTEM-level access under specific conditions. No exploitation of Agent2Shell has been reported at the time of writing.
Are you affected?
You are most likely affected if all of the following are true:
you run an on-premises N-central server, not the hosted service
the server is reachable from the internet or from untrusted networks
the Legacy API is enabled
Check the Legacy API setting in your N-central configuration. If you are unsure whether the server is exposed, check your firewall rules and external scan results.
If you do not run on-premises N-central, or the Legacy API is disabled, the reported attack path does not apply to your environment. Confirm this against N-able's advisory before closing the question.
What to do
Identify all on-premises N-central servers, including test and backup instances. Many organisations have forgotten systems.
Disable the Legacy API where it is not required. The reported attack path depends on it. Confirm the exact steps and any official mitigation in N-able's security advisory, because this article does not replace it.
Restrict access to N-central. Do not expose the server directly to the internet. Limit access to management networks and trusted addresses.
Install the latest N-able updates, but do not treat them as proof that the server is safe. Reports say compromises have occurred on hotfixed servers, so the update alone does not remove the risk.
Search for signs of compromise (see the next section) before assuming the server is clean.
Rebuild compromised servers. A cryptocurrency miner is often the only visible sign of a server-level compromise, but an attacker with root access can have installed other tools. Huntback recommends treating each hit as a full compromise rather than a simple miner cleanup.
Has it already happened to you?
Look for these indicators on N-central servers:
unexpected POST requests to /dms/services/ServerUI in web or application logs
a systemd service named xvd.service that you did not create
processes running XMRig or other mining software
files or directories under /tmp/.xvd or /var/tmp/.xvd
outbound connections to 157[.]20[.]241[.]16, the attacker host reported by Huntback
a downloaded archive named xmrig.tgz, listed among the indicators N-able published on 13 November
Huntress reported that it had not observed exploitation in its partners' environments as of 13 November, so the campaign may not be widespread. Confirm the status of your own servers rather than relying on that finding.
Why it matters more than the miner
Cryptocurrency mining is the only activity reported so far. It does not explain the risk. The real issue is root access on a server that manages other systems. A compromised N-central server could allow an attacker to reach devices across a customer network, install additional tools or steal credentials. The miner is simply the easiest thing to monetise and detect.
The incident also shows a common problem with fast-moving vulnerability disclosures: the exploit can appear before most organisations have had time to apply a fix or change configuration. In this case, an updated server was reported as compromised. That means patching must be paired with reducing exposure, such as disabling unused interfaces, restricting access and monitoring for unusual outbound traffic.