Following the public disclosure of over 30 alleged zero-day vulnerabilities, N-able has taken its hosted N-central environments offline across all major regions and instructed on-premises customers to shut down their systems. The vulnerabilities, which include flaws that could enable complete system compromise, were published by security researcher Sean Bales on Sunday, November 8, along with working proof-of-concept code in a GitHub repository named Able2Shell.

image

N-central is a remote monitoring and management platform deployed by managed service providers and IT teams to oversee and secure customer infrastructure remotely. Bales tested the vulnerabilities against N-central Appliance 2026.4.0.31, a pre-release build, and indicated that most or all of the flaws likely impact earlier versions as well. The researcher confirmed that artificial intelligence assisted in discovering the vulnerabilities.

The disclosed flaws span authentication bypasses, credential exposure, arbitrary file writes, directory traversal, cross-site scripting, XML external entity injection, and remote code execution. Among the most severe is an unauthenticated XXE vulnerability in the service-import function that can be chained to steal authenticated sessions, reset passwords, and run commands as the nable user. The same attack path permits creation of a rogue Default Administrator account with attacker-supplied credentials, granting unauthorized administrative control of the N-central interface.

Bales demonstrated the exploit chain in a video showing successful administrator account creation, authentication, access to restricted administrative features, and command execution under the nable account. Additional disclosed exploits include a stored XSS flaw that executes commands as root when administrators view malicious patch metadata, and a privilege-escalation vulnerability allowing code running under the nable account to escalate to root. Bales identified the unauthenticated XXE-to-RCE chain as the most critical of all disclosed issues.

https://www.youtube.com/embed/wSBr52uIhWs

Global service shutdown and response

N-able declared a critical security incident and brought its hosted N-central infrastructure offline across the Americas, Europe, and Asia-Pacific. Although BleepingComputer has not independently confirmed all reported vulnerabilities, N-able's acknowledgment that it is developing a hotfix suggests at least some of the claimed zero-days are genuine.

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. 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. 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

In a follow-up status report, N-able stated it continues developing and testing a hotfix and has detected no signs of active exploitation or unauthorized access. The N-central classic environment remains unavailable, though N-able confirmed that Ecoverse services accessed through N-able Login continue operating. The company has not announced a timeline for restoring N-central but committed to publishing status updates every four hours or more frequently if circumstances warrant.

Researcher cites unaddressed prior disclosures

Bales explained his decision to publish the N-central vulnerabilities without prior notification to N-able, stating that the company had failed to remediate vulnerabilities he reported in a separate N-able product five to six months earlier. According to Bales, he disclosed two unrelated remote code execution flaws and a privilege-escalation issue in that earlier product, which remain 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

Bales indicated he sent follow-up communications over the preceding four to six weeks without receiving responses. He attributed his decision to bypass N-able's standard disclosure process to frustration with the company's handling of vulnerability reports, stating that his experience demonstrated "they don't take disclosure seriously." The N-central exploits target a different product than his earlier reports. Bales also noted that N-able's bug bounty program did not compensate him for his previous submissions.

Following the disclosure, N-able's leadership, including the CEO and CTO, reached out to Bales requesting removal of the GitHub repository and collaboration on remediation. Bales reported that the executives did not issue threats but simply asked him to take down the repository and work with the company. When BleepingComputer inquired about Bales' allegations regarding the previously reported vulnerabilities, their patching status, and the lack of response to his communications, N-able declined to address those specific questions, offering only its statement on the N-central incident and precautionary measures. The earlier vulnerabilities remain absent from the publicly released Able2Shell repository and allegedly continue unpatched.