Skip to content
NewA calmer, faster ZeroHour

N-able takes hosted N-central offline after Able2Shell PoC release

Original title: Critical vulnerabilities in N-able N-central prompt hosted shutdown

Rapid7 Blogby Rapid7 ()2 min read
Part of a story covered by 9 sourcesN-able keeps N-central offline after Able2Shell disclosureMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

A researcher published proof-of-concept code for 33 issues, including unauthenticated RCE; N-able reports scanning but no confirmed compromises.

On November 9, 2026, N-able said it was responding to the Able2Shell disclosure of critical flaws in its N-central RMM platform. The researcher published details and PoC code for 33 issues, including unauthenticated RCE, root privilege escalation, credential disclosure, and unauthorized account creation. As of November 10, N-able reported scanning tied to the PoC but no evidence of successful customer exploitation, and hosted N-central classic environments remain offline while a hotfix is developed. No CVE identifiers, CVSS scores, full affected range, or remediation build have been published.

Unconfirmed: N-able says it has no evidence of successful exploitation; CVEs, the full affected range, and a fixed build are not yet published.

Key facts
  • One chain combines XXE and session weaknesses to run code as the nable service account.
  • Other chains require an administrator to view malicious patch metadata or use of ProductAdmin credentials.
  • The researcher tested N-central Appliance 2026.4.0.31; the full affected range is unstated.
  • N-able aimed to validate a hotfix by midday November 10 EST and has not named a fixed build.
  • Rapid7 advises taking on-premises servers offline until they are upgraded with the hotfix.
Security assessment · AI, from the articlePublic proof of concept

Impact: Unauthenticated remote code execution as the nable service account

ProductAffected
N-able N-centralN-central Appliance 2026.4.0.31 tested; full range not stated
What to do
  1. 1.Take on-premises N-central servers offline until the hotfix is installed.
  2. 2.Hosted customers should follow N-able service restoration updates.
  3. 3.Review N-central servers and downstream managed systems for compromise.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

From the original article

2 min read at rapid7.com

Overview On November 9, 2026, N-able announced that it was responding to the public disclosure of critical vulnerabilities affecting N-central, its remote monitoring and management (RMM) platform. In a public disclosure titled Able2Shell, an independent researcher has published details and proof-of-concept (PoC) code covering 33 issues.

Rapid7 Blog

By Rapid7 · rapid7.com

Read the full article at Rapid7 Blog

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.