Cybersecurity

N-able 4EverAble2Shell Exploited Within Hours: 21 Servers Compromised, 19 Running HF2

Published By Shivam Sharma9 min read
Compromised N-able N-central servers mining Monero after the 4EverAble2Shell zero-day exploit

4EverAble2Shell exploited within hours of its public release. Attackers used the new exploit chain to compromise at least 21 N-central servers and install Monero cryptocurrency miners, according to security firm Huntback, reported by BleepingComputer. Nineteen of the 21 were running HF2, build 2026.4.1.26, the hotfix N-able had released two days earlier. On 16 November, N-able released Hotfix 3, which removes the Legacy API option entirely.

Hotfix on 10 November, bypass on 11 November

The story starts on 8 November, when independent researcher Sean Bales, known as BinaryNinja, published the Able2Shell repository with details of 33 alleged critical vulnerabilities in N-central, with proof-of-concept code, according to BleepingComputer. On 9 November, N-able took its hosted N-central environments offline worldwide, across the Americas, Europe and Asia-Pacific, and told customers running the product on their own servers to take them offline too. N-able said it had not observed active exploitation as of 9 November at 15:15 UTC and had found no evidence of unauthorised data access. We covered the original disclosure and the worldwide shutdown in our earlier report.

On 10 November, N-able released N-central 2026.4 HF2, build 2026.4.1.26, to address the Able2Shell vulnerabilities. The hotfix addresses seven CVEs, according to Huntress: CVE-2026-125883, CVE-2026-125878, CVE-2026-125879, CVE-2026-125880, CVE-2026-125881, CVE-2026-125882 and CVE-2026-91000. That is 7 of the 33 alleged flaws, about 21%. By 01:04 UTC on 11 November, all hosted N-central servers had been upgraded and hosted environments were back online.

Late on 11 November, Bales published two more sets of exploit code, named 4EverAble2Shell and Agent2Shell, both stated to work against HF2. At 01:10 ET on 12 November, Huntress told customers to treat a fully patched server as vulnerable and to take on-premises servers offline again, even after HF2. Five hours and twenty minutes later, at 06:30 ET, N-able’s advisory clarified that the server issue depends on a non-default configuration in which the Legacy API is turned on and exposed to the public internet, and N-able was not advising customers to take N-central offline. The researcher updated his repository to confirm the exploit only works with Legacy API turned on.

This was not N-central’s first bad month. Huntress had already tracked separate flaws in August 2026, CVE-2026-18556 and CVE-2026-18577, and an actively exploited pre-authentication remote code execution zero-day in September, CVE-2026-86218, with a 10.0 CVSS score. Those are separate incidents from Able2Shell and from 4EverAble2Shell and Agent2Shell.

How 4EverAble2Shell exploited HF2 servers

While the guidance was flipping, the attackers were already moving. Huntback saw the same attacker IP address as Previdian, 157.20.241.16, probing its N-central honeypots at approximately 08:30 UTC on 12 November, with the first attempts to execute the complete exploit chain beginning at 09:16 UTC, according to BleepingComputer. By 12:50 UTC, researchers found 21 active miners using the attacker’s naming convention, all of which had submitted mining shares within the previous five minutes.

The chain, as observed, starts with initial code execution through the Apache Axis flaw CVE-2026-90436, rated CVSS 9.8, running as the nable service account, then escalates to root through 4EverAble2Shell. The miners installed XMRig, a Monero cryptocurrency miner, configured to use about half of the available CPU cores, likely to make the mining harder to detect, according to BleepingComputer. Huntback identified the compromised systems through the attacker’s cryptocurrency mining pool statistics, where infected systems were assigned identifiers beginning with nc_ followed by the server’s IP address. The researchers checked the associated IP addresses and confirmed all 21 hosted N-central installations, including 19 running version 2026.4.1.26.

The compromised servers were located across multiple countries, including the United States, Canada, South Africa, the United Kingdom, Germany, France and Sweden. That is roughly four hours and twenty minutes from the first probe to 21 confirmed compromised servers, and 19 of 21, about 90%, were running HF2, build 2026.4.1.26. Previdian is tracking the privilege escalation flaw as VULN-2026-0009 and has added it to its own Known Exploited Vulnerabilities catalog.

4EverAble2Shell is an unauthenticated remote code execution chain that results in root access on the N-central server and requires no credentials, according to the researcher’s claim, which Huntress’s initial code review supports. Agent2Shell is a set of more than ten issues in how the N-central server communicates with Windows Agents and Probes; two of the chains allow an unauthenticated attacker who can reach the server to run commands on managed Windows endpoints, including as SYSTEM, provided the attacker knows the target appliance ID. Used together, the two sets could let an attacker move from an internet-facing N-central server to the endpoints it manages, according to Huntress’s assessment of the potential impact, not an observed attack.

N-able said one thing, researchers saw another

N-able’s position in its advisory, as carried by BleepingComputer, is that it “had seen no signs of compromise using the new flaws”, while security researchers have since reported successful exploitation against production servers. This is a direct conflict: N-able has not confirmed the compromises, and the researchers’ count comes from mining-pool data. Because 4EverAble2Shell grants full root access, organisations that detect these indicators should treat the breach as a full compromise of the server, according to BleepingComputer.

Security firm watchTowr said it is seeing probes for 4EverAble2Shell targeting N-central builds with the Legacy API enabled. Huntress, for its part, said on 13 November that it had not observed exploitation of these issues in its partners’ environments. Hosted N-central environments are not affected by the new issue, according to N-able, and the incident impacts on-premises N-central in the Americas, Asia-Pacific and Europe.

On 13 November, N-able confirmed that Agent2Shell exploitation, like 4EverAble2Shell, also requires the non-default Legacy API to be enabled. That resolves the biggest open question from the first day, when Huntress was still working with N-able to clarify whether the Agent2Shell chains depended on Legacy API. The same day, N-able published indicators of compromise for customers that have not disabled the Legacy API, including URLs and outbound traffic involving 157.20.241.16, 139.99.69.109 and 79.76.51.56. It also disabled the Intune integration and restricted other features, and said it was working with affected customers.

The internet exposure fell sharply while all this happened. Shadowserver counted 1,338 exposed N-central servers on Monday 9 November; by the time BleepingComputer reported the compromises, the count was just over 148, a drop of about 89%.

Hotfix 3: Legacy APIs are gone for good

On 16 November, N-able released N-central 2026.4 Hotfix 3, a critical security update that supersedes the 10 November hotfix, according to Huntress. The update implements server and user account hardening measures, improves Agents and Probes communications, and adds additional validation to file publishing, file path and XML import handling. The hotfix also removes the configuration option for legacy APIs, a feature that was leveraged in several of the proofs of concept, and N-able states that legacy APIs are now permanently blocked.

N-able began applying the hotfix to hosted N-central environments in a phased rollout on the morning of 16 November before releasing it to the general public in the evening. All customers running on-premise N-central deployments are urged to upgrade their servers as soon as possible. Both hosted and on-premise customers must upgrade all of their Agents and Probes to the latest version to be fully protected, as N-able states that agents and probes that are not upgraded are subject to impersonation.

Hotfix 3 includes 17 CVEs. Several appear to require no login: CVE-2026-129272, a predictable MMS3 appliance passcode; CVE-2026-129274, CVE-2026-129276 and CVE-2026-129277, missing authentication on ServerMMS2 calls; CVE-2026-129278, Take Control audit log tampering; CVE-2026-129279, user enumeration via password reset; and CVE-2026-129280, missing authorisation on ServerUI SOAP calls. Several appear to lead to root or nable-user code execution: CVE-2026-129271, a patch-package local privilege escalation; CVE-2026-129273, an audit export syslog injection; and CVE-2026-129286, a SIS GenericFiles path traversal. The rest appear to be XXE, SSRF and permission gaps: CVE-2026-129275, CVE-2026-129281, CVE-2026-129282, CVE-2026-129283, CVE-2026-129284, CVE-2026-129285 and CVE-2026-129287. No CVSS scores have been assigned yet for these 17, and Huntress says it has not seen evidence of exploitation in the wild for them. These 17 are separate flaws included in Hotfix 3; they are not CVE identifiers for the 4EverAble2Shell or Agent2Shell chains, which still have none.

What should N-central admins do now?

If your N-central server had Legacy API enabled and exposed to the internet, review its activity from 11 November for the indicators below, and treat it as a full compromise if you find any. Apply Hotfix 3 and upgrade every Agent and Probe. The hotfix removes the Legacy API option entirely.

Several of these steps restate Huntress’s and N-able’s published guidance; the rest are general precautions drawn from the findings, not instructions from either.

  1. Upgrade on-premises N-central servers to Hotfix 3 as soon as possible, then upgrade every Agent and Probe.
  2. On servers not yet on Hotfix 3, confirm Legacy API is disabled and keep it off the internet.
  3. Review server and endpoint activity from 11 November onward for all the indicators listed below.
  4. Check for unexpected administrator accounts, new scripts, scheduled tasks and remote sessions on the server.
  5. Treat any server showing the mining indicators as a full compromise of the server, as BleepingComputer recommends.
  6. Do not rely on IP allowlisting alone, since Agents and Probes use the same endpoints to check in.

The indicators Huntress extracted from static code analysis, none of which had been observed in the wild as of 12 November, include POSTs to /dms/services/ServerUI containing jline.internal.TerminalLineSettings or GenericAgentXMPPMessageExchange with SessionID -1, POSTs to /dms2/services2/ServerMMS2 containing RemoteExecutionTaskSubmit with sessionID -1, a file at /var/opt/n-central/flag/flag_default.json existing as a symlink to /opt/nable/var/ncsai/scripts/ServerChild.sh, and serverchild files named serverchild-<12 hex>.bak, .sh or .out. On Windows endpoints, look for encoded PowerShell launched by the N-able Agent as SYSTEM, and changes to wsp.exe or service.cfg in the Windows Software Probe.

What is still unknown

As of 12 November 2026, no CVE identifiers had been assigned to the 4EverAble2Shell or Agent2Shell chains in the sources checked. The 17 CVEs in Hotfix 3 are separate flaws.

Whether all 21 compromised servers had Legacy API enabled. N-able’s narrowing and the 21 compromises have not yet been reconciled in any source checked.

How many servers were affected in total. N-able has not said; only Huntback’s 21 are confirmed, through the mining pool.

Whether CVE-2026-90436 or the N-central chain is in CISA’s Known Exploited Vulnerabilities catalog. Neither was listed as of 16 November, according to the sources checked.

Whether Agent2Shell was used against any managed Windows endpoints. Huntress’s assessment says the chains could let an attacker run commands on endpoints, but no such use has been reported.

Whether Bales publishes a third wave of exploit code, and whether N-able’s status page changes its guidance again.

The 4EverAble2Shell exploited a hotfix that was about two days old. Hotfix 3 removed the Legacy API option and permanently blocked legacy APIs, addressing the condition the server-side exploit required. Nineteen of 21 compromised servers were running HF2, and the lesson is not that patching failed. It is that a patch cannot protect a server whose dangerous setting was left on.