Executive Summary

On November 9th, 2026, N-able announced that it is responding to a public disclosure of critical vulnerabilities in N-central, its remote monitoring and management (RMM) platform. As a precaution, N-able took its Hosted N-central environment offline and advised on-premises customers to take their N-central servers offline until it provides further guidance.

Managed service providers (MSPs) and IT teams use N-central to manage the endpoints and networks they are responsible for. A compromised server can give an attacker a path into every network it manages. Threat actors have targeted N-central before: in October 2026, researchers linked the China-nexus group Volt Typhoon to zero-day exploitation of two earlier N-central flaws.

N-able states it has not seen active exploitation of these vulnerabilities, and at the time of writing no fix is available. Given the administrative reach of N-central servers and past state-sponsored targeting of the platform, Beazley Security recommends affected organizations follow N-able's guidance and take on-premises N-central servers offline as soon as possible, keeping them offline until N-able confirms they can be safely restored.

Beazley Security will continue monitoring developments and provide updates as new information becomes available.

Affected Systems or Products

Product

Affected Versions

Fixed Versions

N-able N-central (on-premises)

Not disclosed by N-able at the time of writing

Not yet available

N-able Hosted N-central

Hosted environment, taken offline by N-able on November 9th, 2026

Not yet available

Mitigations / Workarounds

N-able advises customers running on-premises N-central servers to secure their environments and take the servers offline until N-able confirms they can be safely brought back online. N-able has also taken the Hosted N-central environment offline while it secures and remediates it, so hosted customers cannot reach their environment and related services may be unavailable. N-able has not published a workaround that would let a server stay online safely.

Until N-able releases fixes, the following may help to reduce risk alongside N-able's guidance:

  • Inventory every on-premises N-central server, including test, staging, and disaster recovery instances, and confirm that each one is offline.

  • Where a server cannot be taken offline, it does not meet N-able's guidance. At minimum, remove its internet exposure, restrict access to trusted administrative networks, and treat it as at risk, because the preconditions of the new vulnerabilities are not known.

  • Follow N-able's status page for remediation instructions and confirmation that servers can be restored.

Patches

At the time of writing, N-able has not released fixes. N-able states that it will publish updates and remediation instructions on its status page as they become available. N-able is remediating the Hosted N-central environment itself while it is offline.

Technical Details

At the time of writing, N-able has not published technical details, CVE identifiers, affected versions, or the name of the party that disclosed the vulnerabilities. N-able's incident notice lists a start time of 14:00 UTC on November 9th, 2026, describes the vulnerabilities as critical, and states that N-able has seen no active exploitation. It is not known whether the new flaws are related to earlier N-central vulnerabilities.

Beazley Security will update this advisory when N-able releases technical information or fixes.

How Beazley Security is responding

Beazley Security is monitoring client perimeter devices through our Exposure Management Platform to identify impacted devices and support organizations in remediation of any issues found.

We are also conducting threat hunts across our MDR environment to detect potential exploitation attempts against our clients.

If you believe your organization may have been impacted by this vulnerability and need support, please contact our Incident Response team.

Sources