N-able N-central zero-day exploited hours after PoC release
Threat actors installed XMRig miners on at least 21 N-central servers by 12:50 UTC on November 12, including 19 running the latest hotfix, researchers said.

Security researcher Sean Bales published proof-of-concept exploits for two new N-able N-central zero-days on November 12, and attackers began probing for one of them within hours, BleepingComputer reported. The chain, named 4EverAble2Shell, allows unauthenticated attackers to execute commands as root on servers that have the Legacy API enabled, and Bales said it worked against the latest N-central 2026.4 Hotfix 2 build, 2026.4.1.26. The companion Agent2Shell exploit targets N-central's agent functionality and can execute commands with SYSTEM privileges on managed Windows devices.
The disclosures came two days after N-able released Hotfix 2 to patch seven CVEs from an earlier round of zero-days, Five Nines reported in November. N-able responded by restricting certain N-central features and integrations, including the Intune integration, and told on-premises customers to disable Legacy API access, according to BleepingComputer. In its November 12 advisory, the company said it had seen no signs of compromise using the new flaws. On November 13, N-able said it had identified additional indicators of compromise and was working with affected customers, SecurityWeek reported.
Previdian told BleepingComputer it saw suspicious requests targeting its N-central honeypot at about 08:30 UTC on November 12, and later confirmed attackers attempting the full exploit chain. Huntback observed the same attacker IP address and recorded the first complete exploit at 09:16 UTC, roughly five hours after Bales published the code, the report said. The payload downloaded a shell script from 157.20.241[.]16 that installed an XMRig Monero miner with systemd or cron persistence, limiting it to half of the server's CPU cores. By 12:50 UTC, Huntback found 21 active miners in the attacker's mining pool, all named with an nc_ prefix followed by the server IP address. Nineteen of those servers were running the latest N-central 2026.4 Hotfix 2, released November 10, and the compromised systems were in the United States, Canada, South Africa, the United Kingdom, Germany, France, and Sweden, SecurityWeek reported.
N-able said in its advisory that it had seen no signs of compromise using the new flaws, but researchers subsequently reported successful exploitation of production N-central servers, BleepingComputer noted. The chain first exploits CVE-2026-90436 in the Apache Axis component to run commands as the nable service account, then abuses a separate N-central privilege escalation to gain root. SOCRadar's analysis states that no CVE or fix covers the full N-central chain yet, and disabling the Legacy API is the main control. N-able said hosted N-central is not affected by the server chain because Legacy API is off by default, according to SOCRadar, though the company disabled the Intune integration as a precaution.
Bales also released Agent2Shell, a companion set of more than ten zero-days that he says allows SYSTEM-level command execution on Windows endpoints managed by an N-central agent, SOCRadar reported. No Agent2Shell exploitation has been reported as of November 13. Defenders should disable Legacy API access and hunt for published indicators: POST requests to /dms/services/ServerUI carrying SOAP faults, the user agent python-requests/2.31.0, files under /tmp/.xvd or /var/tmp/.xvd, the systemd service xvd.service, and connections to 157.20.241[.]16. Researchers advise treating any match as a full server compromise, not a cleanup job.
Sources: BleepingComputer, SecurityWeek, SOCRadar, Five Nines
Noor Haddad covers attacks, breach disclosures and exploited vulnerabilities for Five Nines. Noor writes from CISA and vendor advisories, SEC disclosures and published reporting.
Corrections. Report an error to corrections@thefivenines.com. We list substantive corrections on the corrections page.