4EverAble2Shell: From a Security Hotfix to Root Compromise
Summary
A critical exploit chain dubbed 4EverAble2Shell has been disclosed affecting N-able N-central, a remote monitoring and management (RMM) platform used by managed service providers (MSPs) and enterprise IT teams to manage infrastructure, monitor endpoints, deploy software, perform maintenance and administer systems remotely. The attack chain combines an Apache Axis remote code execution vulnerability, CVE-2026-90436, with a separate local privilege-escalation weakness in N-central to obtain root-level access to the underlying server.
The first stage of the attack abuses vulnerable SOAP fault processing in Apache Axis through N-central's Legacy API endpoint, /dms/services/ServerUI. A specially crafted unauthenticated HTTP request can trigger attacker-controlled Java class instantiation, resulting in operating-system command execution under the nable service account. The attacker can subsequently abuse N-central's privileged maintenance functionality and unsafe filesystem handling to escalate privileges from the service account to root.
The combination of these weaknesses allows an unauthenticated remote attacker to progress from network access to root-level compromise of an affected N-central server, provided the required Legacy API functionality is enabled and reachable. The attack is particularly significant because the exploit chain was reportedly demonstrated against N-central 2026.4 Hotfix 2, build 2026.4.1.26, which had been released to address earlier vulnerabilities.
Following the public release of the exploit, attackers were observed attempting to exploit vulnerable installations and deploy XMRig cryptocurrency-mining software. Investigations identified 21 active mining workers associated with N-central servers, with 19 reportedly running Hotfix 2 at the time of observation.
Organizations running N-central should immediately assess whether the Legacy API is enabled, restrict exposure of management interfaces, apply the latest vendor security updates, and investigate for evidence of previous exploitation. Because successful exploitation can result in root-level compromise, systems with confirmed exploitation should not be considered trustworthy simply by removing the miner or applying a security update.
Vulnerability Details
| CVE ID | Severity | CVSS Score | Vulnerability Type |
|---|---|---|---|
| CVE-2026-90436 | Critical | 9.8 | Remote Code Execution (RCE) |
| SVE-110172 | Critical | 9.8 | Local Privilege Escalation |
SVE: SecPod Vulnerability Enumeration.
The exploit chain involves two distinct security weaknesses. CVE-2026-90436 provides the initial remote execution capability through Apache Axis, while the second-stage vulnerability abuses privileged maintenance operations and filesystem trust to elevate the attacker's privileges to root.
Technical Details and Attack Methodology
The 4EverAble2Shell attack chain consists of two stages: The attacker first exploits CVE-2026-90436 in Apache Axis through N-central's Legacy SOAP API to obtain command execution as the nable service account. The attacker then abuses N-central's privileged maintenance functionality and unsafe filesystem handling to escalate privileges from nable to root, ultimately gaining full control of the underlying management server.
1: Remote Code Execution (as nable)
The initial compromise exploits CVE-2026-90436, which involves unsafe processing of SOAP fault messages in Apache Axis, a Java-based framework used for implementing SOAP web services. N-central exposes a legacy SOAP API endpoint at /dms/services/ServerUI, which provides the attack surface for this vulnerability. An unauthenticated attacker can send a specially crafted SOAP request containing attacker-controlled exception information that influences server-side Java class instantiation involving jline.internal.TerminalLineSettings. Under the vulnerable processing conditions, this behavior allows the attacker to trigger command execution on the underlying operating system.
Because the vulnerable Legacy API endpoint can be accessed without a legitimate N-central administrative session under the reported attack conditions, an attacker with network access to the exposed service can exploit the vulnerability without authentication. Successful exploitation provides remote command execution in the context of the N-central nable service account. This initial foothold provides access to processes, filesystem resources and application functionality available to the service account, but does not inherently grant root-level privileges.
2: Local Privilege Escalation (from nable to root)
Following the initial compromise, the attacker exploits a separate local privilege escalation weakness involving N-central's privileged maintenance operations and unsafe filesystem path and symbolic-link handling. The affected functionality includes components such as nable_wrapper.pl, the setLDFileOwner privileged helper, ServerChild.sh, and associated server-control and maintenance workflows.
The privilege escalation abuses privileged maintenance operations that interact with filesystem objects or paths influenced by the lower-privileged nable account without adequately validating their integrity or ownership. By manipulating filesystem state and interfering with the privileged workflow involving ServerChild.sh and associated maintenance operations, the attacker can cause functionality intended to run with elevated permissions to execute in an attacker-controlled context.
By chaining this local privilege escalation with the initial remote code execution foothold, the attacker transitions from execution as nable to root-level command execution on the N-central server. Root access enables control over system processes, application files, configurations, services, scheduled tasks and other host-level resources, resulting in full compromise of the underlying management server.
Post-Exploitation Activity
After obtaining root privileges, attackers can deploy additional payloads, establish persistence and execute post-compromise activities. Observed campaign activity included the deployment of XMRig cryptocurrency-mining software, temporary payload files, and persistence mechanisms involving systemd services and scheduled tasks.
The compromised N-central server can subsequently be abused for sustained unauthorized activity, including cryptocurrency mining, resource hijacking, malicious process execution and continued access to the affected infrastructure.

Threat Activity and Exploitation in the Wild
The disclosure of 4EverAble2Shell was followed by exploitation attempts against exposed N-central servers. Public reporting described a campaign in which attackers used the exploit chain to gain control of N-central installations and deploy cryptocurrency-mining software.
The observed campaign involved XMRig, a mining utility commonly associated with Monero cryptocurrency mining. Once attackers obtained privileged execution on compromised servers, they deployed mining payloads that consumed system resources to generate cryptocurrency for the attacker.
The mining activity reportedly used approximately half of the available CPU cores, potentially allowing the malicious workload to remain active while reducing the likelihood of immediately attracting attention through extreme resource utilization.
Investigators also identified mining-pool worker names using a naming convention beginning with nc_ followed by the affected server's IP address. This naming convention allowed researchers to correlate worker activity with exposed N-central installations and identify compromised infrastructure.
At the time of one investigation, researchers identified 21 active mining workers associated with N-central servers across multiple countries. Of those installations, 19 reportedly identified themselves as running N-central 2026.4 Hotfix 2, build 2026.4.1.26.
The findings demonstrate that deploying an earlier security hotfix does not necessarily eliminate exposure to a newly disclosed exploit chain. However, these figures represent an observed snapshot of mining workers and should not be interpreted as a global count of all compromised N-central servers.
Cryptocurrency mining was the observed campaign objective. Root-level access to an RMM management server also creates broader security risks because the compromised system may possess credentials, integrations and trusted communication relationships with managed infrastructure.
Affected Versions
| Product / Software Branch | Affected Versions | Fixed Version / Mitigation |
|---|---|---|
| N-able N-central | 2026.4 HF2 (2026.4.1.26) and earlier versions | Upgrade to N-central 2026.4 HF3 (2026.4.1.39) or later. Ensure the Legacy API is disabled. |
| Apache Axis 1.x | Versions 1.0 through 1.4 | No official Apache Axis 1.x release fix is available. The project is end-of-life; migrate to a supported alternative. |
Indicators of Compromise (IoCs)
The following indicators are associated with the exploitation of 4EverAble2Shell against N-able N-central servers and the subsequent deployment of cryptocurrency-mining payloads. These indicators include attacker infrastructure, exploit-related HTTP requests, malicious files, persistence mechanisms and suspicious process activity.
Network Indicators
| Indicator | Description |
|---|---|
157.20.241[.]16 |
Attacker infrastructure associated with exploitation, payload hosting and callback activity. Observed ports include 8080 and TCP ports 19202–19418. |
139.99.69[.]109:10128 |
Primary cryptocurrency-mining pool endpoint used by deployed XMRig miners. |
79.76.51[.]56:39100 |
Fallback cryptocurrency-mining pool endpoint used by the miner. |
hxxp://157.20.241[.]16:8080/jup.sh |
Shell script associated with downloading, installing and configuring the cryptocurrency miner. |
hxxp://157.20.241[.]16:8080/xvgz |
Reported cryptocurrency-mining payload download URL. |
hxxp://157.20.241[.]16:8080/xmrig.tgz |
Archive containing the XMRig cryptocurrency-mining payload. |
hxxp://157.20.241[.]16:8080/ob/cronhit |
Miner-related check-in endpoint associated with persistence and status reporting. |
hxxp://157.20.241[.]16:8080/ob/fcheck |
Miner-related check-in or status-check endpoint. |
Request and Log Indicators
| Indicator | Description |
|---|---|
POST /dms/services/ServerUI |
HTTP POST requests targeting the N-central Legacy SOAP API exploited during the initial remote code execution stage. |
jline.internal.TerminalLineSettings |
Java class reference associated with the Apache Axis SOAP fault exploitation path. |
SOAP Fault containing exceptionName |
Suspicious SOAP fault structure associated with exploit requests. Use as a hunting indicator and correlate with the Java class reference and request context. |
python-requests/2.31.0 |
User-Agent string reported in exploit-related HTTP traffic. |
File and Host Indicators
| Indicator | Description |
|---|---|
/tmp/.xvd/ |
Hidden directory associated with cryptocurrency-miner deployment. Reported contents include the miner binary x, watchdog script keep.sh, and mining log xm.log. |
/var/tmp/.xvd/ |
Alternative reported staging or installation directory for the cryptocurrency-mining payload. |
keep.sh |
Watchdog script associated with restarting the miner if the process terminates. |
/etc/systemd/system/xvd.service |
Systemd service used to establish persistence for the cryptocurrency-mining process. |
/etc/cron.d/xvd |
Cron-based persistence mechanism associated with the miner. |
Crontab entry ending with # xvkeep |
Persistence marker associated with miner watchdog scheduling under user or root crontab entries. |
/var/opt/n-central/tmp/serverchild-*.bak |
Backup artifacts associated with the reported local privilege-escalation activity. |
/var/opt/n-central/tmp/serverchild-*.sh |
Shell-script artifacts associated with the N-central privilege-escalation chain. |
/var/opt/n-central/tmp/serverchild-*.out |
Output artifacts associated with execution of the privilege-escalation-related scripts. |
/var/opt/n-central/flag/flag_default.json |
Filesystem object reported as being manipulated through symbolic-link abuse during the privilege-escalation stage. Validate its type and integrity against a known-good installation. |
Process Indicators
| Indicator | Description |
|---|---|
XMRig or renamed miner binary x |
Cryptocurrency-mining process deployed on compromised N-central servers. |
--rig-id nc_ |
Miner command-line argument associated with worker names beginning with nc_, followed by the victim server's IP address. |
--donate-level 1 |
Command-line parameter reported in association with the deployed XMRig miner. |
Behavioral Indicators
- HTTP POST requests to
/dms/services/ServerUIcontaining suspicious SOAP fault structures and references tojline.internal.TerminalLineSettings. - Command execution or shell processes spawned by the N-central
nableservice account following suspicious Legacy API requests. - Unexpected execution of N-central maintenance or server-control functionality accompanied by unauthorized filesystem changes or privilege escalation from
nableto root. - Creation or modification of
serverchild-*.bak,serverchild-*.shorserverchild-*.outfiles within/var/opt/n-central/tmp/. - Unexpected symbolic-link activity involving
/var/opt/n-central/flag/flag_default.jsonor unauthorized modifications to privileged N-central maintenance scripts. - Cryptocurrency-mining processes running from hidden temporary directories, including XMRig or renamed miner binaries, with command-line arguments such as
--rig-id nc_. - Unexpected creation of
xvd.service, cron entries in/etc/cron.d/xvd, or crontab entries containing the marker# xvkeep. - Outbound connections from N-central servers to
157.20.241[.]16,139.99.69[.]109:10128, or79.76.51[.]56:39100associated with payload retrieval, callbacks or cryptocurrency-mining activity. - Unusual CPU consumption associated with unauthorized cryptocurrency-mining processes, reportedly utilizing approximately half of the available CPU cores.
MITRE ATT&CK Mapping
| Technique ID | Technique Name | Tactic ID | Tactic |
|---|---|---|---|
| T1190 | Exploit Public-Facing Application | TA0001 | Initial Access |
| T1068 | Exploitation for Privilege Escalation | TA0004 | Privilege Escalation |
| T1105 | Ingress Tool Transfer | TA0002 | Execution |
| T1496.001 | Resource Hijacking: Compute Hijacking | TA0040 | Impact |
Impact
Successful exploitation of 4EverAble2Shell can result in root-level compromise of the N-central management server. Because N-central is used to centrally administer and monitor managed systems, compromise of the platform can have consequences extending beyond the server itself.
- 1. Unauthorized root-level access to the management server.
- 2. Modification of system files, application configurations and privileged scripts.
- 3. Deployment of additional malware or unauthorized software.
- 4. Cryptocurrency mining and abuse of CPU and other system resources.
- 5. Creation of persistent services or scheduled tasks.
- 6. Potential exposure of credentials, stored configuration information and administrative integrations.
- 7. Abuse of trusted management relationships to potentially affect downstream systems, depending on permissions, integrations and attacker actions.
Mitigation and Recommendations
- 1. Upgrade to the patched N-central release: Upgrade N-central to a security-fixed release. N-central 2026.4 Hotfix 3 (build 2026.4.1.39) includes security changes that address the reported attack path and permanently block the Legacy API. Verify the installed build and follow the vendor's upgrade instructions to ensure the server, Agents and Probes are updated as required.
- 2. Disable the Legacy API: Disable the Legacy API if it is not required for operational purposes. If it must remain enabled, restrict access to trusted management networks, authorized hosts and specific source IP addresses to prevent unauthorized access to the exposed SOAP service.
- 3. Restrict network access to N-central: Avoid exposing the N-central management server and legacy services directly to the internet. Implement firewall rules, network segmentation, access-control lists and dedicated management networks to limit access to authorized administrators and infrastructure.
- 4. Investigate potential exploitation: Review web, application, network and host logs for suspicious requests to
/dms/services/ServerUI, unusual SOAP fault processing, unexpected Java class references and suspicious command execution originating from N-central services. Investigate any activity that may indicate exploitation of the Apache Axis vulnerability. - 5. Inspect privilege escalation and filesystem activity: Examine the
nableservice account activity, privileged helper executions, unexpected ownership changes, modifications toServerChild.sh, suspicious symbolic links and unauthorized changes to N-central maintenance scripts or filesystem resources. - 6. Review credentials and connected infrastructure: Assess credentials accessible to the N-central server, administrative accounts, integrations, Agents, Probes and connected systems. If compromise is suspected, rotate potentially exposed credentials, review privileged account activity and investigate access to other systems from the management server.
- 7. Isolate and rebuild if compromise is confirmed: If root-level compromise is detected, isolate the affected server and preserve evidence for forensic investigation. Patching or removing malicious files alone may not be sufficient. Consider rebuilding N-central from trusted installation media, restoring validated configurations, rotating credentials, validating Agent and Probe integrity, and monitoring the environment for further malicious activity.
Want to Know More About the 4Everable2Shell Security Flaw?
xplore how the 4Everable2Shell vulnerability exposes N-able systems to potential exploitation. Learn how attackers exploit the flaw, understand its technical details and security impact, and discover the mitigation steps organizations can take to protect their systems. View Webinar
Instantly Fix Risks in Endpoints & Cloud with Saner
Saner is a continuous and integrated vulnerability & exposure management platform that instantly fixes risks in endpoints and cloud.




