Back Mezha N-able takes hosted N-central offline after researcher publishes 30+ alleged zero
N-able has taken its hosted N-central environments offline and advised on-premises customers to shut down their servers after a researcher published more than 30 alleged vulnerabilities, including flaws that could enable system takeover.
Late Sunday, November 8, security researcher Sean Bales published a GitHub repository called Able2Shell with proof-of-concept exploits for the vulnerabilities.
This is reported by BleepingComputer .
N-central is a remote monitoring and management platform used by managed service providers and IT teams to monitor, manage and secure customer devices and networks remotely.
Bales said he tested the vulnerabilities against N-central Appliance 2026.4.0.31, a pre-release version, and believes most, if not all, also affect earlier versions.
The disclosed flaws include authentication bypasses, credential disclosure, arbitrary file writes, directory traversal, cross-site scripting (XSS), XML external entity (XXE) injection and remote code execution (RCE).
One of the most critical exploit chains uses an unauthenticated XXE vulnerability in N-central’s service-import function to steal a trusted local session, reset an account password and run commands on the server as the nable user. The exploit can also create an enabled Default Administrator account with attacker-controlled credentials, granting administrative access to the N-central management interface.
Bales published a video demonstration showing terminal output reporting successful administrator account creation, login authentication, access to protected administrative functionality and remote command execution as the nable user.
Other exploits include a stored XSS flaw that can run commands as root when an administrator views malicious patch metadata, and a privilege-escalation flaw that allows code running under the nable account to run commands as root. Bales told BleepingComputer the unauthenticated XXE-to-RCE exploit was the most critical of those disclosed.
After the disclosure, N-able announced a critical security incident and took its hosted N-central environments offline in the Americas, Europe and Asia-Pacific.
BleepingComputer said it had not independently verified all the reported vulnerabilities. N-able confirmed it was developing a hotfix to address the security issues, lending credence to Bales’s claims that at least some of the flaws are legitimate zero-days.
N-able is actively responding to non-responsible communication of critical vulnerabilities in N-central late Sunday night, November 8, found by an independent researcher, – N-able to BleepingComputer
N-able is actively responding to non-responsible communication of critical vulnerabilities in N-central late Sunday night, November 8, found by an independent researcher,
– N-able to BleepingComputer
As a precautionary measure, we took our Hosted N-central environment offline today, November 9, and provided guidance to customers operating on-premises N-central servers to temporarily take their servers offline until further notice. – N-able to BleepingComputer
As a precautionary measure, we took our Hosted N-central environment offline today, November 9, and provided guidance to customers operating on-premises N-central servers to temporarily take their servers offline until further notice.
– N-able to BleepingComputer
Our Security, Engineering, and Operations teams are actively working to implement the necessary remediation. At this time, we have not observed active exploitation of these vulnerabilities. Protecting our customers and their environments remains our highest priority, and we will provide additional updates as they become available. – N-able to BleepingComputer
Our Security, Engineering, and Operations teams are actively working to implement the necessary remediation. At this time, we have not observed active exploitation of these vulnerabilities. Protecting our customers and their environments remains our highest priority, and we will provide additional updates as they become available.
– N-able to BleepingComputer
In a later status update, N-able said it was continuing to develop and validate a hotfix and had found no evidence of active exploitation or unauthorized data access. The company said Ecoverse services accessed through N-able Login remained operational while the N-central classic environment was unavailable.
N-able has not estimated when N-central will return online. It said it plans to publish updates every four hours, or sooner if new information becomes available.
Bales told BleepingComputer he deliberately published the N-central vulnerabilities without notifying N-able beforehand because he alleged the company had failed to address flaws he had previously reported in a different N-able product. He said he had reported two unrelated RCE vulnerabilities and a privilege-escalation flaw five to six months earlier, and that they remained unpatched.
I disclosed 2 unrelated RCEs for a different N-able product, along with a priv esc vulnerability 5 or 6 months ago. These have yet to be patched. I did not disclose any of the 0-days I posted last night, – Sean Bales to BleepingComputer
I disclosed 2 unrelated RCEs for a different N-able product, along with a priv esc vulnerability 5 or 6 months ago. These have yet to be patched. I did not disclose any of the 0-days I posted last night,
– Sean Bales to BleepingComputer
Bales also claimed that he, his manager and his director had sent five follow-up emails over the four to six weeks without receiving a response. He said his experience with N-able’s vulnerability disclosure process and that “they don’t take disclosure seriously” led him to publish the N-central exploits. He said they target a different N-able product from the one involved in his earlier reports.
Bales also claimed he received no payment through N-able’s bug bounty platform for his earlier reports.
Other topics you might like:
Kiteworks urged customers to temporarily shut down servers after receiving a warning a possible imminent cyberattack. The company reported no evidence of a breach in its own systems.
A Pentagon personnel system breach exposed unencrypted personal records of 2.8 million living people and nearly 300,000 deceased, including Social Security numbers and military service details.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
