N-central zero-day hits servers on latest hotfix
The N-able N-central zero-day 4EverAble2Shell hit servers already on Hotfix 2. How the chain works, who's exposed and the setting to turn off now.

On this page 5 sections ▾
WHAT TO DO
- There's no fix for this chain yet. The defense right now is making sure N-central's Legacy API is turned off, which N-able says keeps the server attack out.
- N-able has published indicators of compromise, so any on-premises server that had the Legacy API switched on should be checked for signs it was already hit.
- Affected
- On-premises servers with the Legacy API on, including 2026.4 Hotfix 2
- Fixed in
- No fix yet
- Disclosed
- Nov 6, 2026
- Exploited
- Yes, since November 12, 2026 (not on CISA KEV)
- Workaround
- Turn off the Legacy API
The servers hit by the new N-central zero-day weren't neglected: 19 of the 21 compromised in the first wave were already running N-able's latest hotfix. That fix was real, it just covered a different set of flaws, and this attack came in through a setting that's off by default.
Quick facts
Attackers were compromising servers roughly 5 hours after the exploit code went public.
So far the only payload seen is an XMRig Monero miner, capped at half the server's CPU cores.
The way in is a flaw in Apache Axis 1.x, an end-of-life open-source component bundled inside N-central.
#What happened with N-able N-central
Security researcher Sean Bales published 33 alleged N-central vulnerabilities on GitHub with working exploit code, and N-able took its hosted N-central environments offline the same day. N-able shipped a hotfix, then Bales published two more exploit chains the following night, 4EverAble2Shell and Agent2Shell. The first one was in use against live servers by the next morning.
- N-able takes hosted N-central offline after the first batch of flaws goes public
- N-central 2026.4 Hotfix 2 (build 2026.4.1.26) ships with fixes for seven CVEs from the first batch
- 4EverAble2Shell and Agent2Shell are published
- N-able says the server chain needs the Legacy API turned on and exposed to the internet
- N-able confirms Agent2Shell also needs the Legacy API on, and publishes indicators of compromise for servers that hadn't turned it off
#How the 4EverAble2Shell chain works
It's two flaws joined together. The first is CVE-2026-90436, a critical bug in the Apache Axis 1.x SOAP engine that N-central bundles, which lets an attacker who reaches the Legacy API run commands on the server. The second is a separate, still-unspecified N-central weakness that lifts those commands to root. Together they give an unauthenticated attacker full control of the server.
ELI5: explain it simply▾

THE WORDS
- SOAP
- An older format programs use to send each other structured requests over the web.
- Root
- The all-powerful administrator account on a Linux server.
THE IDEA
Picture an old side door into a building that nobody uses anymore, with a lock from 20 years ago. The first trick gets you through that door as a janitor. The second trick turns the janitor's keys into the master key for every room.
- Two disclosures, one hotfixHotfix 2 fixed seven CVEs from the first batch of flaws. 4EverAble2Shell was published the day after it shipped, so being fully up to date never covered it.
- A component past its end of lifeApache Axis 1.x no longer gets upstream fixes, yet it ships inside N-central. Its flaw was disclosed on November 6, days before anyone chained it to N-central.
- An old switch left onThe Legacy API is off by default and N-able doesn't recommend enabling it. The servers that got hit had it on and reachable from the internet.
#Why an RMM server is the jackpot
N-central is remote monitoring and management (RMM) software: one server that an MSP or IT team uses to patch, script and control every machine it looks after. Root on that server isn't one compromised box, it's a launch point into every client network connected to it. The second chain, Agent2Shell, covers roughly a dozen flaws that could let attackers run commands on those managed Windows agents with System privileges. The attackers so far have only mined cryptocurrency, but the access they had was worth far more.
There's good news on that front: N-able has since confirmed that Agent2Shell, like 4EverAble2Shell, only works when the Legacy API is turned on, so switching it off closes both.
#Is your N-central server exposed?
| System | Status |
|---|---|
| On-premises, Legacy API on and internet-facing (including Hotfix 2) | Exposed |
| On-premises, Legacy API off | Not exposed to the server chain, per N-able |
| Hosted N-central | Not affected by the server chain, per N-able |
- Confirm the Legacy API is offCheck every on-premises server, even if nobody remembers enabling it, using N-able's knowledge-base article on disabling Legacy API settings.
- If it has to stay on, hide itMove the web and SOAP endpoints behind a VPN. N-able's guidance is not to rely on IP allowlisting alone.
- Stay on Hotfix 2 and upgrade Agents and ProbesHotfix 2 still closes flaws from the first batch. All customers, hosted and on-premises, also have to upgrade Agents and Probes, because the hotfix changes how they talk to the server.
#How to check if your N-central server was already hit
Turning the Legacy API off stops the attack, but it doesn't remove anything already installed. Any on-premises server that had the Legacy API on and reachable from the internet, even briefly, should be checked, whether or not it was on Hotfix 2. Researchers at Huntback published what the miner campaign leaves behind:
- FilesA hidden folder at /tmp/.xvd or /var/tmp/.xvd, serverchild- files in /var/opt/n-central/tmp/, and /var/opt/n-central/flag/flag_default.json turned into a symlink.
- PersistenceA systemd service at /etc/systemd/system/xvd.service, a cron file at /etc/cron.d/xvd, or a crontab line ending in # xvkeep. The miner's folder and service are named xvd, not jup.sh, which is only the download script.
- The minerA process whose command line contains --rig-id nc_ or --donate-level 1. Search the command line, not just the name xmrig, because a renamed miner keeps its settings.
- NetworkOutbound connections to 157.20.241[.]16 (port 8080, or ports 19202 to 19418), 139.99.69[.]109 on port 10128, or 79.76.51[.]56 on port 39100.
- The break-inPOST requests to /dms/services/ServerUI from the user agent python-requests/2.31.0 in N-central's web access logs. If you also log request bodies, the exploit shows up as a SOAP fault with an exceptionName field.
The file, persistence and process checks run on the server itself. These are read-only: they look and change nothing. No output from any of them is what you want.
# run as root on the N-central server student@opnf:~$ ls -la /tmp/.xvd /var/tmp/.xvd /etc/systemd/system/xvd.service /etc/cron.d/xvd 2>/dev/null student@opnf:~$ grep -rs xvkeep /var/spool/cron /etc/crontab student@opnf:~$ pgrep -af -- 'rig-id nc_|donate-level 1|xmrig' student@opnf:~$ ls /var/opt/n-central/tmp/ 2>/dev/null | grep serverchild- student@opnf:~$ find /var/opt/n-central/flag/flag_default.json -type l 2>/dev/null # no output from all five means none of these traces are on the server
The network check happens off the server: search firewall, proxy and DNS logs for the three addresses above, going back to November 11, when the chain went public. Those records live elsewhere, so they're still there even if traces on the server were cleaned up.
If you find a match
- Treat it as a full compromiseThe attacker had root, so the miner is just what you can see. Take the server off the network, keep the logs and a disk snapshot, and rebuild it from a known-good install instead of deleting the miner and moving on.
- Rotate everything N-central knowsChange every admin, technician and integration password and API key stored in or used by N-central, because whoever had root could read them.
- Check the machines it managesLook at managed endpoints for new admin accounts, scheduled tasks, scripts and remote sessions since November 11, or since November 8 for servers that weren't on Hotfix 2. On Windows, SYSTEM-level encoded PowerShell started by the N-able agent is worth a look, though it's also common in normal RMM use, so treat it as a lead, not proof.
- Tell N-ableContact N-able support if you find a match. It says it has identified more indicators than the published ones and is working with affected customers.
For your information
A clean result isn't an all-clear. These are the indicators published so far, from the miner campaign researchers have seen. Someone else using the same hole could leave different traces.
Vulnerability management, from reading a CVE to deciding what gets fixed first, is the heart of CySA+. CertPrep+ has study material for CySA+ among its 12 certs from CompTIA, AWS, Microsoft and ISC2: see CertPrep+.
Is 4EverAble2Shell on CISA's KEV list?
What this means for you
If you run N-central on-premises, treat the steps above as tonight's job, not next week's. If you don't, the lesson still travels: an up-to-date server can still be wide open through an old feature someone left switched on.