N-able N-central 4EverAble2Shell exploited, CVE-2026-90436
Attackers are exploiting N-able N-central 4EverAble2Shell (CVE-2026-90436) on servers with Legacy API on, so disable it and check for compromise.
- Published
- Updated
- Fixed in
- not confirmed (N-able planned 2026.4 HF3 after Hotfix 2, build 2026.4.1.26, which does not stop this chain)
- Exploitation
- Yes, Huntback and Lupovis report 21 compromised N-central servers running an XMRig miner, 19 of them on Hotfix 2
Live scores
CVE-2026-90436- EPSS
- 0.011
some chance of attack soon - VEDAS
- 0.939
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
What happened
Independent researcher Sean Bales published proof-of-concept exploits called 4EverAble2Shell and Agent2Shell on November 12, 2026, according to BleepingComputer. They came two days after N-able shipped Hotfix 2 (build 2026.4.1.26) for an earlier batch of flaws, and Bales says they work against that build. opnf.sh dates the publication to late November 11, so the sources differ by a day.
4EverAble2Shell lets an unauthenticated attacker run commands as root on an N-central server. BleepingComputer and SecurityWeek both say it chains an Apache Axis flaw, CVE-2026-90436 (CVSS 9.8), with a separate N-central privilege escalation weakness. Exploitation requires the Legacy API to be enabled. The Hacker News reports that Agent2Shell uses more than 10 zero-day flaws to run commands on managed Windows agents as NT AUTHORITY\SYSTEM, assuming the attacker knows the target appliance ID. opnf.sh reports that N-able confirmed Agent2Shell also needs the Legacy API on.
Exploitation followed within hours:
- Probing: BleepingComputer reports that Previdian saw probing of its honeypot from about 08:30 UTC on November 12 and later full exploit chain attempts. The Hacker News reports that watchTowr also saw probes against builds with the Legacy API enabled.
- Compromised servers: Huntback reports 21 compromised production servers, 19 of them on Hotfix 2, per BleepingComputer and The Hacker News. SecurityWeek quotes Lupovis, which counted 21 rigs: 9 in the US, 4 in South Africa, 4 in Canada, plus the UK, Germany, France and Sweden.
- Payload: The only payload seen so far is an XMRig Monero miner using about half of the CPU cores. The servers downloaded a shell script from 157.20.241[.]16.
- Impact: Huntback cautions that root on this host is access to a system that manages customers’ endpoints. The Hacker News quotes it as saying a hit should be treated as a full compromise.
The sources differ on N-able’s position. BleepingComputer says its November 12 advisory reported no signs of compromise using the new flaws. The Hacker News later reports that N-able confirmed attackers are targeting customers who have not disabled the Legacy API and shared indicators of compromise. SecurityWeek quotes N-able saying it has found additional indicators and is working with those customers.
Per The Hacker News, N-able said on November 16 that 2026.4 HF3 was in testing. The plan was hosted environments first, then on-premises customers on Monday, subject to validation. The headlines list a later The Hacker News article saying N-able patched 17 N-central flaws, and a Rapid7 post reporting exploitation of CVE-2026-90436 against Atlassian Confluence Data Center as well. Their full details are not confirmed here.
Am I affected?
- On-premises N-central with the Legacy API on and exposed to the internet: Yes. This includes servers on Hotfix 2. The Hacker News quotes N-able as saying the Legacy API is off by default and not recommended.
- On-premises with the Legacy API off: not exposed to the server chain, per N-able as relayed by opnf.sh.
- Hosted N-central: N-able says hosted environments are not affected by the server issue (The Hacker News).
- Other products running Apache Axis: the headline of the Rapid7 post indicates CVE-2026-90436 has been exploited in Atlassian Confluence Data Center too. Whether your other software is affected is not confirmed here.
What to do now
- Disable Legacy API access on every on-premises N-central server, even if nobody remembers enabling it. BleepingComputer and The Hacker News both report N-able urging this.
- Keep Hotfix 2 and upgrade Agents and Probes as N-able advises, since the hotfix changes how they communicate (The Hacker News). Hotfix 2 alone does not stop this chain. Watch for 2026.4 HF3 availability, which is not confirmed as released in these sources.
- Look for signs of exploitation, as BleepingComputer reports from Huntback:
- requests to /dms/services/ServerUI, especially ones referencing jline.internal.TerminalLineSettings;
- an unexpected xvd.service systemd service;
- mining processes;
- files under /tmp/.xvd or /var/tmp/.xvd.
- Search firewall and proxy logs for N-able’s published indicators, per The Hacker News:
- 157.20.241[.]16 (port 8080, and ports 19202 to 19418);
- 139.99.69[.]109 on port 10128;
- 79.76.51[.]56 on port 39100.
- If you find a match, treat the server as fully compromised, as Huntback advises. opnf.sh suggests isolating it, keeping logs and a disk snapshot, rebuilding from a known-good install, rotating credentials stored in N-central, reviewing managed endpoints, and contacting N-able support. These are that outlet’s recommendations, not N-able’s.
- A clean result is not an all-clear. opnf.sh notes the published indicators come from one miner campaign, and other attackers could leave different traces.
Sources
- The Hacker News: New N-central Exploits Work Against Patched Servers, Enable Root RCE and Windows SYSTEM Access
- BleepingComputer: New N-able “4EverAble2Shell” zero-day exploited hours after PoC released
- The Hacker News: Hackers Exploit N-central Flaws to Infect 21 Servers, Including 19 Running Hotfix 2
- SecurityWeek: Hackers Exploit New N-central Zero-Day Hours After PoC Publication
- opnf.sh: N-central zero-day hits servers on latest hotfix
- Rapid7: Rapid7 Detected Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center, N-able N-central also Exploited (headline only)
- The Hacker News: N-able Patches 17 N-central Flaws as Attackers Exploit Earlier Bugs to Deploy Crypto Miners (headline only)
- NVD: CVE-2026-90436