Security Digest · Nov 9, 2026 · Vulnerability · Other

Able2Shell: N-central Zero-Days, HF3 Now Available

N-central 2026.4 HF3 (2026.4.1.39) fixes 17 more CVEs and permanently blocks the Legacy API abused by 4EverAble2Shell. Upgrade servers, agents, probes.

Our verdict

Act now

Upgrade on-premises N-central to 2026.4 HF3, which permanently blocks the exploited Legacy API, then upgrade every Agent and Probe and hunt for compromise from the HF2 window.

Who must act: Every managed service provider and IT team running N-central on-premises, and hosted customers too, because all Agents and Probes must be upgraded to HF3.

Who can relax: Organizations with no N-central server and no MSP using one. N-able has named only N-central, and N-able.app services behind N-able Login remain online.

Affected
N-able N-central on-premises before 2026.4.1.39 (2026.4 HF3)
N-central 2026.4.1.26 (HF2) and earlier with the Legacy API enabled: 4EverAble2Shell (unauthenticated root RCE, exploited)
Agents and Probes not yet upgraded to 2026.4.1 HF3, on hosted and on-premises deployments: susceptible to impersonation, per N-able
Fixed in
N-central 2026.4.1.39 (2026.4 HF3), released Nov 16, 2026: fixes 17 CVEs (CVE-2026-129271 to CVE-2026-129287) and permanently blocks legacy APIs
N-central 2026.4.1.26 (2026.4 HF2), released Nov 10, 2026: fixed seven CVEs from the original disclosure
Hosted N-central: server upgraded by N-able; customers must still upgrade Agents and Probes
CVSS
9.8 (v3.1, CISA-ADP)
EPSS
3.8% (percentile 90)
CISA KEV
Yes, listed as known exploited
Exploitation
Exploited in the wild
Severity
Critical

What to do

  1. Upgrade on-premises N-central to 2026.4.1.39 (HF3); it installs directly over 2025.4 and later builds, including HF1 and HF2.
  2. Upgrade every Agent and Probe to 2026.4.1 HF3, on hosted and on-premises alike, even those already on HF2, then review the Inactive Assets tab.
  3. Until HF3 is installed, confirm the Legacy API is disabled and keep the server off the internet or behind a VPN.
  4. Hunt for compromise now: check for an xvd.service unit, /tmp/.xvd or /var/tmp/.xvd, and miner processes, and treat any hit as full root compromise.
  5. Before changing anything on a suspect server, snapshot it and export firewall, proxy and VPN logs from Nov 8 onward.
  6. Review N-central accounts, scripts, scheduled tasks and agent-run commands on managed devices since Nov 8.
  7. If the server was internet-reachable after Nov 9, rotate credentials used by discovery and scripts, starting with domain accounts.

How to check if you are affected or compromised

  • Search web and proxy logs for POST requests to /dms/services/ServerUI, especially bodies mentioning jline.internal.TerminalLineSettings.
  • On the server, run systemctl status xvd.service and ls -la /tmp/.xvd /var/tmp/.xvd, and look for xmrig or unexplained CPU use.
  • Check firewall logs for traffic to or from 157.20.241.16, 139.99.69.109 and 79.76.51.56, the addresses Rapid7 relays from N-able's Nov 13 update.
  • On the server, list recently changed web files: find /opt/nable/webapps -name '*.jsp' -newermt 2026-11-08 -ls, and check files owned by nable changed since then.
  • Do not treat clean logs as proof. ThreatDefence warns that the original XXE chain removes its staging logs.

What happened#

Late on November 8 US time, independent researcher Sean Bales published Able2Shell, a repository of 33 N-able N-central vulnerabilities with proof-of-concept exploits. N-central is a remote monitoring and management (RMM) platform used largely by managed service providers. Bales told BleepingComputer the work was AI-assisted and that he did not warn N-able first. The findings include XML external entity injection, OGNL injection, stored XSS, path traversal and an escalation from the nable service account to root. Huntress counted at least four exploit chains. N-able took Hosted N-central offline on November 9 and told on-premises customers to shut down their servers.

On November 10, N-able shipped N-central 2026.4 HF2 (build 2026.4.1.26). It fixes seven CVEs, among them XXE (CVE-2026-125883), OGNL injection (CVE-2026-125878), root escalation through syslog-ng configuration (CVE-2026-125879) and upload path traversal leading to RCE (CVE-2026-125882).

Update, November 12–16: 4EverAble2Shell is exploited#

On November 12, Bales published 4EverAble2Shell, an unauthenticated-to-root chain tested against HF2. It needs the Legacy API to be enabled. The entry point is CVE-2026-90436, a flaw in Apache Axis 1.x, which N-central bundles. When it parses a SOAP fault, Axis loads whatever class the request names, before any authentication handler runs. CISA's ADP scores it 9.8. Axis 1.x is end-of-life and no release will fix it. Previdian says the chain gets commands as nable through an attacker-chosen JLine class, then abuses N-central's privileged helpers to reach root. Bales also released Agent2Shell, which The Hacker News reports runs commands as SYSTEM on managed Windows agents if the attacker knows the appliance ID.

Exploitation started within hours. BleepingComputer reports that Huntback saw full-chain attempts from 09:16 UTC that installed an XMRig Monero miner. By 12:50 UTC it counted 21 compromised servers mining, 19 of them on HF2. Previdian logged attempts from eight attacker IPs through November 16. N-able's November 12 advisory says the Legacy API is off by default and should stay off, and that it disabled the Intune integration as a precaution. We could not open that advisory, which returned HTTP 403, so its statements are as reported by BleepingComputer and The Hacker News. HF3, described below, followed on November 16.

Update, November 16–17: HF3 fixes 17 more CVEs and removes the Legacy API#

On November 16, N-able released N-central 2026.4 HF3 (build 2026.4.1.39). It fixes 17 CVEs, CVE-2026-129271 through CVE-2026-129287. They include an authentication bypass through a predictable passcode (CVE-2026-129272), root command execution through Audit Export syslog injection (CVE-2026-129273), path traversal leading to RCE (CVE-2026-129286), two XXE flaws and several endpoints that lacked authentication. The release notes give no CVSS scores. HF3 also removes the Legacy API configuration option, so legacy APIs are permanently blocked. That closes the entry point 4EverAble2Shell used.

Two points are easy to miss. First, every Agent and Probe must be upgraded to 2026.4.1 HF3, including those already on HF2, for hosted and on-premises customers alike. N-able says those left behind are "susceptible to impersonation." Second, devices now need an SMBIOS ID or machine ID to connect, so check the Inactive Assets tab after upgrading. Remote control other than Take Control is disabled, and the Intune integration remains blocked. SecurityWeek reports that Bales then published details of 24 more N-central flaws, which he says are fixed by the latest patches.

The Axis flaw reaches beyond N-central. Rapid7 detected exploitation of CVE-2026-90436 against Atlassian Confluence Data Center on November 13. Confluence 1.x through 9.x is affected when the Remote API (XML-RPC & SOAP) is enabled, which is not the default. The fix is 9.2.28 or a current 10.x release. On November 18, CISA added CVE-2026-90436 to its Known Exploited Vulnerabilities catalog with a November 21 deadline, warning that affected products may be end-of-life and that users should stop using or replace them. Any other product that bundles Axis 1.x deserves the same check.

Who is affected#

Every on-premises N-central server older than HF3 is missing fixes. HF2 and older servers with the Legacy API enabled are exposed to 4EverAble2Shell. Hosted and on-premises customers alike have Agents and Probes to upgrade. N-able says hosted environments are not affected by the new chain. The wider risk is downstream: N-central agents run as SYSTEM or root on managed devices, so one compromised server can reach every client it manages.

Do you really need to act?#

Yes, if you run N-central. The first wave was public exploits with no patch. The second was confirmed compromise of servers on HF2. HF3 closes that path, but only once the server, Agents and Probes are all upgraded. Observed attacks so far install cryptominers. The miner reportedly uses about half the CPU cores to stay unnoticed. Root on an RMM server is worth far more than mining, though, so treat any hit as a full breach. The Legacy API precondition is real, but the researcher says it got enabled during his own earlier testing, so check it rather than assume the default.

What to do now#

  1. Upgrade on-premises servers to HF3 (2026.4.1.39). It installs directly over 2025.4 and later, including HF1 and HF2. Until then, confirm the Legacy API is disabled and keep the server off the internet or behind a VPN.
  2. Upgrade every Agent and Probe to 2026.4.1 HF3, on hosted and on-premises alike, then review the Inactive Assets tab.
  3. Hunt for compromise on the server: systemctl status xvd.service, ls -la /tmp/.xvd /var/tmp/.xvd, and ps aux --sort=-%cpu | head.
  4. Before cleaning a suspect server, snapshot it and export firewall, proxy and VPN logs from November 8 onward.
  5. Review accounts, scripts, scheduled tasks and Automation Manager policies since November 8, and hunt managed devices for agent-run commands nobody scheduled.
  6. If the server was internet-reachable after November 9, rotate credentials used by discovery and scripts, starting with domain accounts.

How to tell if you were hit#

For 4EverAble2Shell, search logs for requests to /dms/services/ServerUI, especially those referencing jline.internal.TerminalLineSettings, and for traffic to or from 157.20.241.16, the address BleepingComputer reports serving the attack script, plus 139.99.69.109 and 79.76.51.56, which Rapid7 relays from N-able's November 13 update. Installing HF3 does not clean a server that was compromised while on HF2. For the original chains, ThreatDefence suggests find /opt/nable/webapps -name '*.jsp' -newermt 2026-11-08 -ls, grep -rn 'program(' /etc/syslog-ng/ and outbound requests for /external.dtd. The XXE chain reportedly removes its staging logs, so clean logs are not proof. If you find anything, involve incident response and assume managed client networks may be affected.

Timeline#

  • — CVE-2026-90436 published for Apache Axis 1.x.
  • — Able2Shell published. N-able takes hosted N-central offline and tells on-premises customers to shut down.
  • — N-central 2026.4 HF2 (2026.4.1.26) released with seven CVE fixes.
  • — 4EverAble2Shell and Agent2Shell published. Exploitation of HF2 servers begins within hours, and 21 compromised servers are counted.
  • — Rapid7 detects CVE-2026-90436 exploitation against Confluence Data Center.
  • — N-central 2026.4 HF3 (2026.4.1.39) released: 17 more CVE fixes, legacy APIs permanently blocked.
  • — CISA adds Apache Axis CVE-2026-90436 to KEV, due November 21.

Vulnerability records

  • CVE-2026-90436 · KEV 2026-11-18 · ** UNSUPPORTED WHEN ASSIGNED ** Deserialization of an inbound SOAP fault in Apache Axis 1.x allows unauthenticated remote class instantiation.
  • CVE-2026-125878 · Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in N-able N-central allows Resource Injection.
  • CVE-2026-125879 · Incorrect privilege assignment vulnerability in N-able N-central allows Privilege Escalation.
  • CVE-2026-125880 · Improper neutralization of HTTP headers for scripting syntax vulnerability in N-able N-central allows Cross-Site Scripting (XSS).
  • CVE-2026-125881 · Server-Side request forgery (SSRF) vulnerability in N-able N-central allows Server Side Request Forgery.
  • CVE-2026-125882 · Relative path traversal vulnerability in N-able N-central allows Path Traversal.
  • CVE-2026-125883 · Improper restriction of XML external entity reference vulnerability in N-able N-central allows XML Schema Poisoning.
  • CVE-2026-91000 · Missing authentication for critical function vulnerability in N-able N-central allows Privilege Escalation.
  • CVE-2026-129271 · The Patch Management Engine in N-central is vulnerable to LPE via attacker controlled metadata
  • CVE-2026-129272 · N-able N-central before 2026.4.1 HF3 uses a predictable credential to authenticate appliances to an agent-facing API.
  • CVE-2026-129273 · N-able N-central before 2026.4.1 HF3 does not neutralise control characters in an Audit Export setting before writing it to the system logging configuration.
  • CVE-2026-129274 · N-able N-central before 2026.4.1 HF3 does not authenticate callers of the ServerMMS2 RemoteExecutionTaskSubmit operation or verify task ownership.
  • CVE-2026-129275 · N-able N-central before 2026.4.1 HF3 allows the repositoryItemGet operation to be called without authentication.
  • CVE-2026-129276 · N-able N-central before 2026.4.1 HF3 does not authenticate callers of the ServerMMS2 AssetDiscoSimplifiedInfoSubmit operation.
  • CVE-2026-129277 · N-able N-central before 2026.4.1 HF3 does not authenticate callers of the MaintActionGet operation.
  • CVE-2026-129278 · N-able N-central before 2026.4.1 HF3 does not authenticate callers of the ServerII2 remoteControlMSPAStartEndTimeSubmit operation.
  • CVE-2026-129279 · The password reset function in N-able N-central before 2026.4.1 HF3 returns distinguishable responses for valid and invalid accounts.
  • CVE-2026-129280 · Multiple ServerUI and ServerUI2 SOAP operations in N-able N-central before 2026.4.1 HF3 do not verify the caller's session, permissions or customer scope.
  • CVE-2026-129281 · N-able N-central before 2026.4.1 HF3 checks only a view permission for ServerII2 operations that write device execution configuration.
  • CVE-2026-129282 · The test email delivery function in N-able N-central before 2026.4.1 HF3 does not check permissions, lacks CSRF protection, and passes sender and recipient…
  • CVE-2026-129283 · The custom service import in N-able N-central before 2026.4.1 HF3 processes XML external entities.
  • CVE-2026-129284 · N-able N-central before 2026.4.1 HF3 does not validate connection targets in the Report Manager and Data Export settings.
  • CVE-2026-129285 · N-able N-central before 2026.4.1 HF3 does not verify that an action response received over XMPP originates from the appliance the request was sent to.
  • CVE-2026-129286 · N-able N-central before 2026.4.1 HF3 does not validate version values and download locations in software update metadata.
  • CVE-2026-129287 · N-able N-central before 2026.4.1 HF3 processes XML external entities in software repository files.

Sources

Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.

Original and primary sources

  1. Sean Bales — Able2Shell repository (N-central findings and proof-of-concept index) github.com
  2. N-able — N-central critical security incident status page uptime.n-able.com
  3. N-able — Status release notes (N-central 2026.4 HF1) status.n-able.com
  4. N-able — N-central 2026.4 HF2 release notes status.n-able.com
  5. N-able — N-central 2026.4 HF3 release notes status.n-able.com
  6. CVE Program — CVE-2026-90436 (Apache Axis 1.x SOAP fault class instantiation) cve.org
  7. CISA — CISA Adds Four Known Exploited Vulnerabilities to Catalog (Nov 18, 2026) cisa.gov
  8. Sean Bales — 4EverAble2Shell proof-of-concept README github.com
  9. Previdian — VULN-2026-0009: N-central remote code execution (4EverAble2Shell) previdian.com
  10. Huntress — N-able Disables Cloud Services Following Disclosure of Able2Shell Exploit Chains huntress.com
  11. ThreatDefence — N-central Able2Shell Zero-Days: Response and Hunting threatdefence.com
  12. Rapid7 — Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center; N-able N-central also exploited rapid7.com

Coverage and analysis

  1. BleepingComputer — N-able takes cloud platform offline after 30+ zero-days published bleepingcomputer.com
  2. The Hacker News — N-able Takes N-central Cloud Offline After Researcher Discloses 33 Zero-Days with PoC Exploits thehackernews.com
  3. BleepingComputer — New N-able 4EverAble2Shell zero-day exploited hours after PoC released bleepingcomputer.com
  4. The Hacker News — New N-central Exploits Work Against Patched Servers thehackernews.com
  5. SecurityWeek — N-able Kills Legacy APIs, Patches 17 N-central Zero-Days securityweek.com