Skip to content
Able2Shell – Alleged Pre-Auth RCE Exploit Chains (33 Unconfirmed Zero-Days) – N-able N

Able2Shell – Alleged Pre-Auth RCE Exploit Chains (33 Unconfirmed Zero-Days) – N-able N

Ionix • November 10, 2026

Exploit details and PoC code for 33 alleged N-able N-central zero-days ("Able2Shell") were published publicly, likely including unauthenticated RCE. IONIX Research Labs is working to validate the credibility of the findings, is tracking the situation closely, and will update this post with any news.

On November 9, 2026 , an independent researcher publicly released details of 33 alleged critical vulnerabilities in N-able N-central , an on-premises remote monitoring and management (RMM) platform widely used by managed service providers. The disclosure, dubbed "Able2Shell" , was published on GitHub together with technical write-ups and Python proof-of-concept code. According to the researcher, the flaws can be chained into four exploit chains: three leading to remote code execution and one to privilege escalation to root .

In response, N-able took its hosted N-central environment offline as a precaution and instructed on-premises customers to take their N-central servers offline and keep them offline until N-able confirms it is safe to restore them. A hotfix is in preparation.

Status: unconfirmed. No CVE IDs have been assigned yet, and the vulnerabilities have not been independently verified. N-able states it has not observed active exploitation as of November 9, 2026, 15:15 UTC. However, public PoC code is available, and N-central has been the target of multiple actively exploited zero-days in 2026 (CVE-2026-18556, CVE-2026-18577, CVE-2026-86218), so exploitation attempts against internet-exposed servers should be expected.

Reported vulnerability classes (alleged)

Unauthenticated XML External Entity (XXE) leading to remote code execution

Privilege escalation and creation of administrator accounts

Credential disclosure and configuration tampering

Account enumeration and audit-record manipulation

Remote-control session disruption and device impersonation

N-able N-central Appliance 2026.4.0.31, and likely earlier versions (per public reporting). Affected and fixed versions have not yet been confirmed by the vendor.

A compromised N-central server gives an attacker administrative control over every endpoint it manages, including the ability to push scripts, deploy software and open remote-control sessions into downstream customer networks. Earlier in 2026, attackers used exactly this path to reach managed customer environments.

Mitigation and recommended actions

Immediate : Follow N-able’s guidance. Take on-premises N-central servers offline, or at minimum remove all internet exposure of the N-central web interface, and keep them offline until N-able confirms it is safe to restore.

When available : Apply N-able’s hotfix before bringing servers back online.

Investigate : Review N-central login and authentication activity from November 8, 2026 onward. Check audit logs for new administrator accounts, unexpected privilege changes, newly deployed scripts or software, and anomalous remote-control sessions.

If compromise is suspected : Engage incident response, rotate N-central administrator, service-account and integration credentials, and assess the managed endpoints and client networks for follow-on activity.

How IONIX identifies potentially affected assets

IONIX detects the N-able N-central web interface exposed on assets in your attack surface.

IONIX will update this post as N-able publishes CVE identifiers, affected versions and a hotfix, or as IONIX Research Labs has new findings to .

N-able Status Dashboard – Hosted N-central taken offline

GovInfoSecurity: N-able Takes Platform Offline After 33 Zero-Days Drop