N-able N-central Offline After Able2Shell Zero-Days

A researcher published exploit code for what Huntress counts as 33 critical N-able N-central flaws on November 8. N-able took hosted N-central offline, told on-premises customers to shut their servers down, and on November 10 published seven CVEs and a hotfix. What is confirmed, what is not, and what MSPs and IT teams should check.

A long aisle between rows of open grey metal equipment cabinets under a steel-truss warehouse roof
Photo by İsmail Enes Ayhan on Unsplash

Reported as of November 11, 2026, 05:00 UTC. We will add dated updates here if confirmed facts change.

N-able has taken its cloud-hosted N-central service offline and told customers who run N-central on their own servers to shut them down, after an independent researcher published exploit code for dozens of unpatched flaws on Sunday, November 8. N-central is a remote monitoring and management (RMM) platform: managed service providers (MSPs) and IT teams use it to push scripts, patches and remote sessions to the machines they manage, which is why a takeover of the server can reach every downstream customer.

On November 10 N-able published seven CVE records and, per CSO Online, an emergency hotfix. N-able says it has no evidence of successful exploitation of customer environments. Below: what is confirmed, what is not, and what to check if N-central is in your environment.

Timeline

Date (2026)EventSource
Aug 3 to Sep 8Three earlier N-central flaws added to CISA’s Known Exploited Vulnerabilities (KEV) catalog: CVE-2026-18577, CVE-2026-18556, CVE-2026-86218CISA KEV data
Sun Nov 8Researcher publishes “Able2Shell” exploit chains on GitHubTechCrunch
Nov 9N-able takes hosted N-central offline; says no active exploitation seen as of 15:15 UTC; tells customers to keep servers offline until it confirms they can be restoredHuntress, Cybersecurity News
Nov 9 to 10watchTowr reports exploitation attempts against N-central honeypots; Defused reports probingCybersecurity News
Nov 10N-able publishes seven CVE records; hotfix N-central 2026.4 HF2 reportedCVE records (below), CSO Online

Confirmed vs not confirmed

ClaimStatus
Hosted N-central taken offline by N-ableConfirmed by N-able’s status page, as quoted by TechCrunch
On-premises customers told to take servers offlineConfirmed: N-able guidance reported by Huntress, TechCrunch and CSO Online
Seven CVEs, affected versions before 26.4.1Confirmed in N-able’s own CVE records
33 vulnerabilities in four chainsResearcher’s count, as summarised by Huntress; N-able has not said how many it reproduced (CSO Online)
Exploitation of customer environmentsNot confirmed: N-able says it has no evidence of successful exploitation
Exploitation attempts against internet-facing N-centralReported by watchTowr (honeypots) and Defused (probing), via Cybersecurity News
Hosted service restoredNot confirmed by us at the time of writing

Why the researcher published

TechCrunch reports the researcher told BleepingComputer he released the exploits because N-able allegedly failed to patch flaws he had reported in a different product. That is his account; we have not seen N-able respond to it.

The seven CVEs

All seven records were published on November 10, 2026 by N-able as the CVE Numbering Authority, with CVSS v4.0 scores from N-able. We read them from the CVE Program’s cvelistV5 repository.

CVETitle (as published)CWECVSS v4Privileges required
CVE-2026-125883Multiple XXE VulnerabilitiesCWE-6119.3 CriticalNone
CVE-2026-125881Schema-hint SSRF via service import schema validationCWE-9189.3 CriticalNone
CVE-2026-125878Multiple OGNL Injection vulnerabilitiesCWE-798.7 HighLow
CVE-2026-125879Local privilege escalation to root via nable-writable syslog-ng configCWE-2668.6 HighHigh
CVE-2026-125882RCE via file repository upload path traversalCWE-238.6 HighHigh
CVE-2026-91000Insecure IPC Channels lead to local privilege escalationCWE-3068.4 HighLow (local)
CVE-2026-125880Stored XSS via MMS3 patch metadata (admin context)CWE-6448.3 HighHigh

Two details worth noticing if you automate on CVE data:

  • Six records say “before 26.4.1”; CVE-2026-91000 says “before 2026.4.1”, both with versionType custom. The product’s own builds are named like 2026.4.0.31, and the hotfix is reported as “2026.4 HF2”. A naive version comparison can mis-handle that mix; our guide to CVE affected versions, lessThan and versionType explains why custom ranges need a human check.
  • CVE-2026-125878 is titled OGNL injection but carries CWE-79 (cross-site scripting). That is how N-able filed it; it may be corrected later.

None of the seven is in CISA’s KEV catalog as of catalog version 2026.11.10 (released November 10, 19:03 UTC). Five older N-central CVEs are, the three from 2026 listed above plus CVE-2025-8875 and CVE-2025-8876. If you watch the feed, our KEV JSON field guide shows how to match it against your inventory.

How the attack works (as far as sources say)

Huntress describes four chains: three end in remote code execution on the N-central server and one escalates to root. Cybersecurity News notes one public proof of concept chains an XXE flaw into unauthenticated remote code execution. The CVE records confirm two flaws exploitable over the network with no privileges (XXE and SSRF, both 9.3) and two local paths to root (syslog-ng config and insecure IPC).

The exposure matters because of what N-central does. An attacker who controls the server can use it as designed: open remote sessions, deploy scripts and create administrator accounts across managed endpoints. Huntress’s guidance focuses on exactly those downstream actions.

What to check in your environment

From Huntress, N-able’s guidance as reported, and the CVE records:

  1. On-premises N-central: keep it offline until you can patch. Then apply the hotfix and, per CSO Online, upgrade Agents and Probes as well, or they will lose compatibility with the server.
  2. Review authentication from November 8 onward. Huntress recommends checking login and authentication activity for unauthorized access, and involving incident response if you find any.
  3. Look downstream. Anomalous remote access sessions, newly deployed scripts, and new administrator accounts on N-central and on managed endpoints.
  4. Check exposure. If your N-central console was reachable from the internet between November 8 and patching, treat the probing reported by watchTowr and Defused as relevant to you.
  5. Hosted customers: follow N-able’s status page; you cannot patch the hosted service yourself. Plan for how you will reach managed endpoints without your RMM during the outage.

For a broader take on deciding what to patch first when several signals compete, see our vulnerability prioritization workflow. Here the decision is easier than most: a public exploit, unauthenticated network flaws and a tool with administrative reach over every managed machine.

What is not known yet

  • Whether any customer environment was compromised. N-able’s statement is “no evidence”, and it has not said what logging that conclusion rests on.
  • How many of the 33 published issues the hotfix addresses; seven CVEs were assigned.
  • When hosted N-central will be fully restored.

Sources and verification

Important claimSourceStatus
Hosted N-central offline; N-able status page wording; “no evidence of successful exploitation”; on-prem customers told to go offlineTechCrunch, Nov 10Verified (N-able status page quoted; we could not load the page directly)
33 vulnerabilities, four chains, build 2026.4.0.31, no active exploitation as of Nov 9 15:15 UTC, review guidanceHuntress, Nov 9Verified; count is the researcher’s
Hotfix 2026.4 HF2; agents and probes must be upgraded; N-able has not confirmed how many flaws it reproducedCSO Online, Nov 10Qualified: trade press, not an N-able document we could read
watchTowr honeypot exploitation attempts; Defused probingCybersecurity News, Nov 10Qualified: secondary report of vendor statements
Seven CVEs, titles, CWEs, CVSS v4, affected rangesN-able CVE records in cvelistV5, e.g. CVE-2026-125883Verified
Older N-central KEV entries; new CVEs not in KEVCISA KEV catalog, version 2026.11.10Verified

Frequently asked questions

What is Able2Shell?

Able2Shell is the name the researcher gave to the exploit chains published on GitHub on November 8, 2026 against N-able N-central. Huntress describes 33 critical vulnerabilities forming four chains: three lead to remote code execution and one to privilege escalation to root. The research targeted N-central Appliance 2026.4.0.31; earlier versions are likely affected, per Huntress.

Is there a patch for the N-central Able2Shell vulnerabilities?

Yes. CSO Online reports N-able shipped an emergency hotfix, N-central 2026.4 HF2, on November 10, and that customers must also upgrade Agents and Probes to restore compatibility. N-able's seven CVE records, published the same day, list N-central versions before 26.4.1 as affected. N-able has not said how many of the 33 published issues it reproduced.

Has N-central been exploited in the wild?

Not confirmed for customer environments. N-able said it had not seen active exploitation as of November 9 at 15:15 UTC, and TechCrunch quotes it as having 'no evidence of successful exploitation against any of its customer environments.' watchTowr reported exploitation attempts against N-central honeypots after the disclosure. None of the seven new CVEs is in CISA's KEV catalog as of version 2026.11.10.

Is the hosted N-central service back online?

We could not confirm restoration at the time of writing. N-able's status page said hosted N-central was offline 'while we take the necessary actions to secure the environments and implement appropriate remediation,' as quoted by TechCrunch on November 10. Check N-able's status page for the current state.

Hacking NewsN-AbleN-CentralRmmMsp SecurityZero-DayAble2shellIncident Response