Skip to content
TrustList
Security advisories

N-able ships N-central 2026.4 Hotfix 3 as a critical security update

Editorial

By TrustList Editorial

N-able has released N-central 2026.4 Hotfix 3, a critical security update that hardens authentication, file handling and agent connections and blocks legacy APIs, and says agents and probes left on older versions can be impersonated.

About N-able ships N-central 2026.4 Hotfix 3 as a critical security update

N-able ships N-central 2026.4 Hotfix 3 as a critical security update

16 November 2026: N-able has released N-central 2026.4 Hotfix 3, posting the release notes on its status site. The company calls it "a critical security update". It follows the warning earlier this month that hosted N-central had been switched off and on-premises servers should be kept offline after the Able2Shell flaws were published with working attack chains, when no fixed version was yet available.

Not yet independently verified. N-able's release notes do not list CVE numbers or say which reported flaws the hotfix closes. Press reports link it to the attacks on N-central reported in November and give CVE numbers that we did not confirm on an N-able page, so they are not repeated here. We will update this when it can be confirmed, and remove this note.

What the hotfix changes

The hotfix includes everything in Hotfix 2 and adds, according to N-able:

  • missing authentication and permission checks on more server operations;
  • better authentication and session handling when agents and probes talk to the N-central server, separate from the agent-to-probe changes in Hotfix 2;
  • extra validation for file publishing, file paths and XML import;
  • hardening of how the server handles incoming requests and makes outbound connections;
  • the end of legacy APIs: the setting that allowed them is gone, and they are now permanently blocked;
  • improvements to how user accounts are managed and secured.

The release also adds an Inactive Assets tab under Configuration, Asset Discovery, Discovered Assets, which lists agents that N-central has made inactive next to the active agent for the same device, with options to set one active, delete it or export the list.

Servers and agents both need updating

N-able says customers running N-central on their own servers should upgrade them as soon as possible, while hosted servers are upgraded by N-able. The point that is easy to miss is the second one: all customers, hosted and on-premises, must upgrade every agent and probe to the latest version to be fully protected. In N-able's words, "Agents and Probes that are not upgraded are susceptible to impersonation."

What managed service providers should do

On-premises operators should take a backup, install Hotfix 3 and confirm the build afterwards. Everyone should then push the new agent and probe versions to every customer site and track the rollout until no older agents remain, using the new Inactive Assets tab to review devices with duplicate or inactive agents. Any integration that still used the legacy APIs will stop working, so check scripts and third-party tools that connect to N-central and move them to the supported API.

Because the flaws were attacked before a fix existed, treat servers that were reachable from the internet as possibly compromised: review administrator accounts, scheduled tasks, scripts pushed to endpoints and unexpected software on managed devices since early November, and rotate the credentials that N-central stores for customer systems.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in