All CVEs

4EverAble2Shell (N-able N-central): public exploit chain gives unauthenticated root on on-prem N-central servers with Legacy API enabled. It uses Apache Axis CVE-2026-90436 (CISA KEV, added 18 Nov, due 21 Nov). Huntback found miners on 21 servers within hours (most on Hotfix 2); N-able reported attacks on 13 Nov. Fix: upgrade the server to 2026.4 HF3 (2026.4.1.39), which removes the Legacy API, and update Agents and Probes. Until then, make sure Legacy API is off, and check for xvd.service or /tmp/.xvd. Hosted N-central: N-able says not vulnerable. https://tldrcve.com/4everable2shell/

N-able N-central · CVE-2026-90436 · aka Able2Shell, Agent2Shell (sibling chains)

4EverAble2Shell

Patch nowExploited, no login. Axis bug in KEV, due 21 Nov.

A public exploit chain gives an attacker root on on-prem N-central servers that have the old Legacy API turned on, with no login. It gets in through an Apache Axis bug (CVE-2026-90436); the N-central root step has no CVE yet. Security firm Huntback found crypto miners on 21 servers within hours, and N-able reported attacks on 13 Nov.

How scary is it?

updated 20 Nov
  • Yes: Works without logging in3,7
  • Yes: Public exploit code is out3,5
  • Yes: Attacks seen in the wild3,5
  • Yes: On CISA's exploited list (fix by 21 Nov)1,2

Scare-o-meter

Drop everything

Attackers are already on it.
Patch now.

Are you affected? only if all are true

1On-prem N-central below 2026.4 HF3

Hotfix 2 (2026.4.1.26, 10 Nov) does not stop this chain; the exploit was tested on it. Hotfix 3 (2026.4.1.39, 16 Nov) removes the Legacy API. N-able says hosted N-central is not vulnerable to the server chain and gets HF3 automatically.3,4,5,6

2Legacy API is enabled

Off by default, but admins can turn it on under Administration > Mail and Network Settings > Network Security > LEGACY APIS. N-able and the researcher agree the server chain needs it on and reachable.3,4,8

3Attacker can reach the server

No login needed: the Axis bug fires while the SOAP request is parsed, before any per-service auth runs. N-able says the server chain needs the Legacy API enabled and exposed to the internet.7,4

What to do

1Upgrade to 2026.4 HF3 (2026.4.1.39)

Rapid7 says apply it as an emergency, outside normal patch cycles. HF3 permanently blocks the Legacy API and fixes 17 new CVEs. Also update all Agents and Probes to 2026.4.1 HF3, and Patch Management Engine to 2.14.4.5829 or later.4,5,6

Latest safe versions checked 20 Nov

N-able N-central → Server 2026.42026.4.1.39 (HF3)Agents and Probes2026.4.1 HF3Patch Management Engine2.14.4.5829Agents and Probes have no published build number.
2Until then: turn off Legacy API

Make sure the LEGACY APIS setting is off, even on HF2. If you truly need it, never expose it to the internet.4,5,8

3Hunt for compromisecommand

Look in web logs for requests to /dms/services/ServerUI that mention jline.internal.TerminalLineSettings, an unexpected xvd.service unit, mining processes, files in /tmp/.xvd or /var/tmp/.xvd, and traffic to 157.20.241[.]16. If found, treat the server as fully owned (root).3,4

systemctl status xvd.service; ls -la /tmp/.xvd /var/tmp/.xvd
4Then clean up downstream

A hacked RMM server reaches every managed client. Rotate secrets stored in Automation Manager policies, enforce MFA on N-central accounts, and review activity from 11 Nov on for new accounts, scripts, scheduled tasks and remote sessions. The same Axis bug was also exploited against Confluence Data Center on 13 Nov.4,5

This page shows you how to check. It can't tell you you're safe.

Sources (9) and changelog
  1. CISA KEV: CVE-2026-90436 added 18 Nov, due 21 Nov 18 Nov
  2. CISA alert: four KEV additions incl. Apache Axis 18 Nov
  3. BleepingComputer: chain, 21 miners, IoCs, N-able response 12 Nov
  4. Huntress: timeline, HF3 build, actions 17 Nov
  5. Rapid7: CVE-2026-90436 exploited, HF3 guidance 17 Nov
  6. N-able: remediation update, HF3 removes Legacy API 16 Nov
  7. NVD: CVE-2026-90436, Axis 1.x through 1.4, no fix release 6 Nov
  8. N-able docs: where the Legacy API setting lives
  9. Tenable: Able2Shell FAQ 16 Nov