N-able takes hosted N-central offline after researcher publishes over 30 alleged zero-days
TLDR
- N-able released N-central 2026.4 Hotfix 3 on 16 November, fixing 17 CVEs and permanently removing the Legacy API.2829
- Upgrade all Agents and Probes to HF3 or remain open to impersonation; Intune and non-Take Control remote control stay blocked.2930
- Rapid7 says N-able reported N-central exploitation on 13 November; Bales published 24 more flaws he says are patched.283132
N-able took its hosted N-central environments offline on 9 November and urged customers running N-central on their own servers to take them offline until further notice, after a researcher published proof-of-concept exploits for more than 30 alleged vulnerabilities, BleepingComputer reports.1 N-central is a remote monitoring and management platform used by managed service providers and IT teams.1 GovInfoSecurity reports that N-able declared an active incident at 15:15 UTC, citing a major outage of hosted N-central and a "public disclosure and non-responsible communication of critical vulnerabilities".3 N-able told BleepingComputer it took the hosted environment offline "as a precautionary measure", and BleepingComputer says this covers the Americas, Europe and Asia-Pacific.1 N-able has not given an estimate for N-central coming back online and plans updates every four hours, BleepingComputer says, while Ecoverse services accessed through N-able Login remain operational.1
The disclosure is a GitHub repository titled Able2Shell. Its README says testing was done on N-central Appliance 2026.4.0.31, a pre-release version, that most if not all of the vulnerabilities should work on previous versions including the most up to date one, and that all were unpatched at the time of posting.8 The commit that added the material is dated 9 November at 04:14 UTC.9 The README indexes 33 vulnerabilities, and Huntress says they can be chained into four exploits, three leading to remote code execution and one to privilege escalation to root.28 BleepingComputer says the most critical chain abuses an unauthenticated XXE flaw in the service-import function to steal a trusted local session, reset an account password and run commands as the nable user, and can also create an enabled Default Administrator account.1 The researcher confirmed to BleepingComputer that this was the most critical of the disclosed flaws, and BleepingComputer adds that it has not independently verified all of them.1 Other exploits include a stored XSS that can run commands as root when an administrator views malicious patch metadata.1
BleepingComputer says more than 30 vulnerabilities; Huntress, GovInfoSecurity, Field Effect, TechTarget and eSentire say 33, matching the README index.1234578 BleepingComputer and TechTarget put the disclosure on Sunday 8 November, GovInfoSecurity says it was dropped on Monday, and the repository commit is timed 04:14 UTC on 9 November.1359 On who published it, BleepingComputer and GovInfoSecurity name Sean Bales, Field Effect and eSentire refer to a GitHub account named Oracle-Security, and TechTarget says the account belongs to a researcher using the handle BinaryNinja.13457 On confirmation, BleepingComputer says N-able's work on a hotfix lends credence to the claim that at least some of the flaws are legitimate zero-days, while eSentire says N-able has not directly connected the release to its advisory and Field Effect says the chains are alleged and their impact depends on them working as described.147 Bales told BleepingComputer he released the exploits without notice because N-able had not patched flaws he reported in a different product five to six months ago; N-able did not answer BleepingComputer's questions about that.1
On exploitation, N-able told BleepingComputer it had not observed active exploitation, and in a later status update said it had found no evidence of active exploitation or unauthorised data access.1 Previdian reports that from about 22:00 UTC on 9 November one of its N-central decoys received SOAP requests to the service-import endpoints from a single source, some requesting files such as /etc/passwd, but says it has not seen the full published sequence and full exploitation is not confirmed.6 Previdian adds that, when it reported, no CVE had been assigned to that chain and it was not in CISA's Known Exploited Vulnerabilities catalogue.6 On affected versions, Huntress says the flaws affect 2026.4.0.31 "and likely earlier versions as well", and BleepingComputer says the researcher believes most, if not all, also affect earlier versions.12 Huntress advises reviewing login and authentication activity from 8 November onward, and Field Effect advises reviewing administrator-account and configuration changes and rotating N-central administration and integration credentials if unauthorised activity is found.24 Huntress lists earlier 2026 N-central flaws, including CVE-2026-86218, which it calls an actively exploited pre-authentication remote code execution zero-day with a CVSS score of 10.0.2
Update, 11 November 2026: N-able has released N-central 2026.4 Hotfix 2, build 2026.4.1.26, which its release notes, posted on 10 November, describe as a critical security update.10 The notes say it supersedes 2026.4 (build 2026.4.0.27) and Hotfix 1 (build 2026.4.0.32), that on-premises customers should upgrade their servers as soon as possible, and that N-able upgrades hosted servers itself.10 All customers, hosted and on-premises, must also upgrade their Agents and Probes, and N-able advises upgrading Agents first, because an upgraded Probe cannot communicate with an Agent until the Agent and the Patch Management Engine are also at 2026.4.1.26 or later.10 The notes list one known issue: built-in remote control is temporarily disabled and will be re-enabled in a future fix, while Take Control continues to work.10 CSO Online reports that Huntress cautioned that patched servers may not display a new version number, so administrators should verify fixes against N-able's guidance rather than the version string.11
The release notes list seven CVEs fixed by the hotfix: CVE-2026-125883 (multiple XXE vulnerabilities), CVE-2026-125878 (multiple OGNL injection vulnerabilities), CVE-2026-125879 (local privilege escalation to root via a syslog-ng configuration the nable user can write), CVE-2026-125880 (stored XSS via MMS3 patch metadata, admin context), CVE-2026-125881 (server-side request forgery via service import schema validation), CVE-2026-125882 (remote code execution via file repository upload path traversal, credited to Nate Fair of Sprocket Security) and CVE-2026-91000 (insecure IPC channels leading to local privilege escalation).10 CSO Online says N-able has not confirmed how many of the 33 published flaws it could reproduce.11 On service restoration, The Hacker News reports that as of 5:42 p.m. UTC on 10 November N-able said validating activities were ongoing to ensure the fixed version was ready for deployment.12
On exploitation, CSO Online reports that N-able said it has observed scanning activity associated with the published exploits but has not seen evidence that any customer environment has been successfully exploited, and TechCrunch reports that an N-able spokesperson did not respond to a question about whether the company can check, for example through server logs.1114 Sophos X-Ops says third-party reporting suggests exploitation in the wild, that N-able's advisory does not say it has observed exploitation, and that Sophos had not observed exploitation itself.13 The Hacker News reports that watchTowr said it observed exploitation attempts against N-central honeypots overnight, and that Defused Cyber said it saw anonymous agent sessions opened, appliance configuration pulled and the remote control endpoint hit without authentication.12 CSO Online says Previdian recorded 68 exploitation attempts against one of its honeypots from a single IP address within about 18 hours of publication, and that Censys found 1,728 internet-exposed N-central instances.11 TechCrunch gives the researcher's name as Ben Bales, while BleepingComputer, CSO Online and The Hacker News say Sean Bales.1111214
Update, 12 November 2026: N-able said in a post on 11 November that it has upgraded the hosted N-central servers and that they are back online, and that on-premises customers should upgrade to Hotfix 2 as soon as possible and keep their servers inaccessible to the internet until the upgrade is complete.15 N-able says every identified vulnerability that could be exploited by an unauthenticated user has been addressed, and that the remaining ones need an authenticated N-central account, often with elevated privileges, or other limiting conditions, and will be fixed in later hotfixes, with a follow-up hotfix planned.15 Tenable says N-able has not mapped its seven CVEs to the researcher's 33 findings, and Infosecurity Magazine says proof-of-concept code for all 33 remains public.1618 Tenable also reports N-able's CVSSv4 scores for the seven CVEs, ranging from 8.3 to 9.3, with CVE-2026-125883 (XXE) and CVE-2026-125881 (SSRF) the two at 9.3, that CVE-2026-91000 was reserved on 14 September, before the disclosure, and that Hotfix 2 removes legacy mobile device management.16
On exploitation, N-able says it is observing scanning activity associated with the published proof-of-concept code but has seen no indications of compromise within hosted N-central servers, and that confirming whether an individual customer environment was compromised requires an assessment of that environment.15 Tenable says none of the seven CVEs was in CISA's Known Exploited Vulnerabilities catalogue as of 10 November, that Huntress had not observed exploitation in its partners' environments, that Beazley Security Labs said a confirmed compromise of a customer server had not been reported, and that no threat actor had been identified.16 NHS England Digital, in an alert published on 11 November, says security researchers have observed exploitation attempts in the wild, that its National CSOC assesses further exploitation as likely, and that organisations are strongly recommended to take N-central servers offline until the patch can be applied.20 Cybersecurity Dive reports that watchTowr observed probing within 12 hours of the disclosures and later saw exploitation attempts matching the proof-of-concept code, and quotes watchTowr's Yordan Ganchev as expecting further hotfixes.19 BleepingComputer reports that Shadowserver counts just over 148 internet-exposed N-central servers, down from 1,338 detected on Monday.17
N-able says claims that it ignored responsible disclosure from the researcher are inaccurate and that the vulnerabilities published on 9 November were not disclosed through its established reporting channels, which include a bug bounty programme.1519 Sean Bales told Infosecurity Magazine that N-able's account was accurate and that he had not disclosed any of the vulnerabilities to the company, adding that he believed the claim came from an outdated README that he has since changed.18 N-able's chief executive John Pagliuca told Infosecurity Magazine that publishing exploit code before customers could act "hands attackers a head start", and told Cybersecurity Dive that the disclosure was made without proper coordination and had not been verified.1819
Update, 13 November 2026: Sean Bales published two further exploit chains for N-central on 12 November, 4EverAble2Shell and Agent2Shell, saying they were tested against 2026.4.1.26 HF2, the build N-able released on 10 November, BleepingComputer reports.21 According to the researcher, The Hacker News reports, 4EverAble2Shell gives unauthenticated remote code execution as root, while Agent2Shell uses more than 10 zero-day vulnerabilities to run commands as NT AUTHORITY\SYSTEM on managed Windows agents if the attacker knows the target appliance ID.22 BleepingComputer says the 4EverAble2Shell chain needs the Legacy API enabled and combines Apache Axis CVE-2026-90436 with a separate N-central privilege escalation weakness.21 The Apache Axis announcement of 6 November rates CVE-2026-90436 critical, says it affects Axis 1.x through 1.4, which is end of life, and says the project does not expect to release a fixed 1.x version, pointing instead to a patch commit; The Hacker News gives a CVSS score of 9.8 and says patches were released on 6 November.2225 The security firm huntback puts the exploit upload at 03:58 UTC on 12 November, citing the repository's commit history, while GovInfoSecurity says Bales released the chains on Wednesday.2324
N-able said in a 12 November advisory that the server issue depends on a non-default configuration in which the Legacy API is turned on and exposed to the public internet, that the API is off by default and not recommended, and that hosted environments are not affected, The Hacker News reports; it lists the on-premises services in the Americas, Asia-Pacific and Europe as impacted.22 GovInfoSecurity reports that N-able declared an active incident at 07:00 UTC on Thursday and told customers to disable the Legacy API or confirm it is off, and that Bales then updated his GitHub repository to say the Legacy API must be enabled, writing that the Legacy API had been left turned on during earlier testing.23 N-able later said it is restricting certain N-central features and integrations, which may affect some functionality, and BleepingComputer adds that N-able disabled the Intune integration, applied the protections to hosted environments and still asks customers to keep upgrading Agents and Probes.2123 N-able said it had seen no signs of compromise.2123 Bales told BleepingComputer that N-able has not patched two unrelated remote code execution flaws in a different product that were disclosed in July, while GovInfoSecurity describes remote code execution and privilege-escalation flaws disclosed over five months ago.2123 SecurityWeek lists CVE-2026-125878 as XSS flaws with a CVSS score of 8.7, whereas N-able's release notes describe it as multiple OGNL injection vulnerabilities.1027
On exploitation, huntback reports that 157.20.241[.]16 sent its first 4EverAble2Shell check to its N-central decoys at 08:30 UTC on 12 November and ran the full chain from 09:16 UTC: Axis code execution as the nable user, escalation to root, then installation of an XMRig Monero miner.24 At 12:50 UTC the miner pool listed 21 rigs named after server addresses, all submitting shares within the previous five minutes; huntback says all 21 serve N-central pages, 19 report build 2026.4.1.26 (Hotfix 2), and they sit in the United States (9), South Africa (4), Canada (4) and the United Kingdom, Germany, France and Sweden (one each).24 BleepingComputer says Previdian saw the same probing from about 08:30 UTC, tracks the privilege escalation flaw as VULN-2026-0009, and that servers showing the indicators should be treated as fully compromised.21 The Hacker News says there was no evidence of successful exploitation as of writing, reports Previdian's Ryan Dewhurst as saying these are the first documented exploitation attempts against CVE-2026-90436, and reports that watchTowr saw probes for 4EverAble2Shell against builds with the Legacy API enabled.22 GovInfoSecurity reports that Huntress had not observed exploitation in its partners' environments as of Thursday morning.23 The Canadian Centre for Cyber Security says in an advisory dated 12 November that open-source reporting indicates CVE-2026-125883, one of the seven CVEs fixed in Hotfix 2, is exploited in the wild.26
Update, 18 November 2026: N-able released N-central 2026.4 Hotfix 3, build 2026.4.1.39, on 16 November, and its release notes describe it as a critical security update that builds on Hotfix 2.29 The notes list 17 CVEs, CVE-2026-129271 to CVE-2026-129287, and SecurityWeek describes them as zero-day vulnerabilities recently dropped online, covering privilege escalation, predictable passcode, command execution, missing authentication or authorisation, audit log tampering, user enumeration, XXE injection, SSRF and RCE.2829 N-able says the hotfix resolves the authenticated-access vulnerabilities from the first publication and permanently removes access to the Legacy API by deleting its configuration option, which SecurityWeek says blocks exploitation of 4EverAble2Shell.282930 Hosted servers are upgraded by N-able, on-premises customers must upgrade their own servers, and all customers, hosted or on-premises, must upgrade every Agent and Probe, because Agents and Probes that are not upgraded are susceptible to impersonation.29 The notes also add a requirement that devices expose an SMBIOS ID or machine ID, otherwise N-central rejects the connection, and a new Inactive Assets tab for managing Agents.29 Remote control other than Take Control and the Intune integration remain blocked.2930
N-able says its next release will re-enable the Intune integration and remote control after remediation and will address data-leakage issues that require privileged account access, which it calls lower risk, and that this will fully resolve the vulnerabilities that were not responsibly disclosed.30 Its account of the second publication says Agent impersonation requires an attacker to already have a foothold on an endpoint, and would let them receive the same information an Agent receives and set the same values.30 SecurityWeek and The Hacker News report that Sean Bales has since published technical details of 24 more N-central vulnerabilities, stating that they are patched and should not work against the latest patch.2831 The Canadian Centre for Cyber Security's advisory AV26-1165, dated 17 November, lists N-central prior to 2026.4.1 HF3 and the Patch Management Component prior to 2.14.4.5829 as affected.33
On exploitation, Rapid7 says N-able reported exploitation in the wild on 13 November against N-central for a vulnerability that strongly correlates to CVE-2026-90436, and that N-able's incident update of that date lists three IP addresses as indicators of compromise for customers who had not disabled the Legacy API: 157.20.241[.]16, 139.99.69[.]109 and 79.76.51[.]56.32 The Hacker News reports that attackers are using 4EverAble2Shell to deploy cryptocurrency miners.31 Rapid7 advises N-central users to upgrade to Hotfix 3 on an emergency basis outside normal patching cycles, and on-premises administrators still on Hotfix 2 to confirm the Legacy API is disabled.32 Rapid7 also detected exploitation on 13 November of CVE-2026-90436, the Axis flaw in the 4EverAble2Shell chain, against Atlassian Confluence Data Center.2832
Why it matters: N-able says Agents and Probes not upgraded to Hotfix 3 are susceptible to impersonation, Rapid7 advises N-central users to upgrade to Hotfix 3 on an emergency basis, and on-premises operators still on Hotfix 2 to confirm the Legacy API is disabled.2932
Sources
- N-able takes cloud platform offline after 30+ "zero-days" published (BleepingComputer)
- N-able Disables Cloud Services Following Disclosure of "Able2Shell" Exploit Chains (Huntress)
- N-able Takes Platform Offline After 33 Zero-Days Drop (GovInfoSecurity)
- N-able takes N-central offline as alleged zero-day exploits surface (Field Effect)
- N-able takes N-central platform offline after zero-day dump (TechTarget)
- N-able N-central Critical Vulnerabilities: What We Know So Far (Previdian)
- N-able N-Central Vulnerabilities Publicly Disclosed (eSentire)
- Able2Shell - N-Central N-Able (Oracle-Security on GitHub)
- N-Able 0-Days (Oracle-Security on GitHub)
- N-central 2026.4 HF2 Release Notes (N-able Status)
- N-able N-central gets emergency fix two days after 33 exploits published (CSO Online)
- N-able Takes N-central Cloud Offline After Researcher Discloses 33 Zero-Days with PoC Exploits (The Hacker News)
- N-able issues advisory on critical vulnerabilities (Sophos)
- N-able takes its remote access service offline after researcher publishes dozens of zero-day bugs (TechCrunch)
- Update on N-central 2026.4 HF2 and ongoing security response (N-able)
- Able2Shell: Frequently asked questions for reported N-able N-central zero-day vulnerabilities (Tenable)
- N-able releases security hotfixes for zero-day vulnerabilities (BleepingComputer)
- N-able Rushes Out N-central Fixes After 33 Zero-Days Go Public (Infosecurity Magazine)
- N-able issues hotfix after researcher dumps PoCs in disclosure spat (Cybersecurity Dive)
- N-able Releases Security Update for N-central (NHS England Digital)
- New N-able "4EverAble2Shell" zero-day exploited hours after PoC released (BleepingComputer)
- New N-central Exploits Work Against Patched Servers, Enable Root RCE and Windows SYSTEM Access (The Hacker News)
- Researcher Drops More Zero-Day Exploits for N-Able Software (GovInfoSecurity)
- 4EverAble2Shell exploited: Monero miners on live N-central (huntback)
- CVE-2026-90436: Apache Axis 1.x (EOL): unauthenticated remote class instantiation via SOAP fault exceptionName (Apache Axis mailing list (ASF Mailing List Archives))
- N-able security advisory (AV26-1143) (Canadian Centre for Cyber Security)
- Hackers Target N-central Zero-Days as N-able Rushes Patches (SecurityWeek)
- N-able Kills Legacy APIs, Patches 17 N-central Zero-Days (SecurityWeek)
- N-central 2026.4 HF3 Release Notes (N-able Status)
- N-able Vulnerability Remediation Update (N-able)
- N-able Patches 17 N-central Flaws as Attackers Exploit Earlier Bugs to Deploy Crypto Miners (The Hacker News)
- Rapid7 Detected Exploitation of CVE-2026-90436 against Atlassian Confluence Data Center, N-able N-central also Exploited (Rapid7)
- N-able security advisory (AV26-1165) (Canadian Centre for Cyber Security)