Twenty-one on-premises N-central RMM servers were running XMRig Monero miners within four and a half hours of the first exploit attempt. Nineteen of those servers were on N-able's latest Hotfix 2 build. That is the opening count from CVE-2026-90436, a CVSS 9.8 pre-authentication flaw in the Apache Axis 1.x library bundled inside N-central, chained with an unpatched N-central privilege escalation to deliver root command execution. The exploit is called 4EverAble2Shell. No patch exists as of this writing.
What is 4EverAble2Shell?
4EverAble2Shell is a zero-day exploit chain targeting N-able N-central, the RMM platform used by managed service providers. Stage one exploits CVE-2026-90436 in Apache Axis 1.x, a SOAP library bundled inside N-central's /dms/ web interface and end-of-life since 2010. Apache Axis passes the class name from a client-supplied SOAP fault element directly to Java's Class.forName() without validation. An attacker sends an HTTP POST to /dms/services/ServerUI with a body referencing jline.internal.TerminalLineSettings, causing Axis to instantiate the class and execute code as the nable service account. Stage two is a separate unpatched N-central privilege escalation that promotes that service account to root on the Linux appliance. No authentication is required at any step. The only precondition is that Legacy API mode is enabled, which is on by default in older deployments.
Why patching to Hotfix 2 did not protect the servers
N-able released Hotfix 2 in October 2026 as an emergency response to the original Able2Shell disclosure. Huntback researchers monitoring honeypot N-central instances confirmed that 19 of the 21 servers compromised on November 12, 2026 were already running Hotfix 2 build 2026.4.1.26 at the time of compromise. The 4EverAble2Shell chain shares the same /dms/services/ServerUI entry point as the original Able2Shell chain. Hotfix 2 did not close that entry point. MSPs who applied the patch immediately had reasonable grounds to believe they were protected. They were not, unless they had also disabled Legacy API mode as part of remediation.
The one setting that closes the attack entry point
Disabling Legacy API mode in N-central removes the /dms/services/ServerUI endpoint that CVE-2026-90436 targets. Navigate to Administration, then Security, then Legacy API in the N-central console and disable the setting. Organizations that completed October Able2Shell remediation and disabled Legacy API at that time are also protected against 4EverAble2Shell, because both chains enter through the same endpoint. After disabling, verify the setting is saved and confirm that requests to /dms/services/ return an error from an external test host. If Legacy API cannot be disabled immediately, restrict network access to the N-central management ports (80, 443, 10000) so only trusted internal IP ranges can reach the appliance.
What to do right now
- Disable Legacy API mode in N-central under Administration, Security, Legacy API. This removes the exploitable endpoint and breaks the attack chain before stage one completes.
- Firewall the N-central management console from internet exposure. Restrict access to management ports to trusted internal IP ranges until N-able releases a build that removes or sandboxes the Apache Axis 1.x library.
- Check for compromise indicators on N-central Linux appliances: running xmrig processes, presence of /tmp/.xvd or /var/tmp/.xvd staging directories, and a systemd service named xvd.service. Block attacker infrastructure at 157.20.241.16.
An MSP's N-central console typically manages hundreds to thousands of customer endpoints. Full compromise of the console gives an attacker command execution on every managed device without additional lateral movement. Closing the entry point is the first step. Auditing managed endpoints for the companion Agent2Shell indicators is the second.