N-able fixed several paths, but deployment has two parts

N-able calls N-central 2026.4 Hotfix 2 a critical security update. Build 2026.4.1.26 includes fixes across authentication, file handling, server hardening and Agent–Probe communication. Its release notes list seven CVEs fixed by the hotfix, including file-repository path traversal and privilege-escalation issues.

N-able upgrades hosted N-central servers. Customers running on-premises servers must upgrade those themselves. Both groups still need to update their Agents and Probes. That distinction matters for managed service providers who might see a hosted server come back online and assume their rollout is complete.

Check the compatibility order

N-able says to upgrade Agents before Probes. An upgraded Probe cannot communicate with an older Agent or Patch Management Engine until those components reach compatible versions.

Treat this as an environment-wide change

  1. 1

    Confirm the server state. For on-premises N-central, plan the 2026.4.1.26 upgrade using N-able's supported paths. For hosted service, confirm N-able has applied its server update.

  2. 2

    Upgrade Agents, then Probes. Follow N-able's order and check Patch Management Engine compatibility. Test features that depend on Agent–Probe communication, including offline patch caching.

  3. 3

    Review the exposed interval. Preserve relevant server, authentication and administrative logs from the disclosure window. Investigate unusual access or changes using evidence from the specific deployment.

A release note is the boundary for claims

Public reporting described a larger set of alleged flaws. N-able's hotfix note identifies the CVEs it says this build fixes. Keep that distinction in the incident record and watch the vendor status page for any further remediation guidance. Avoid treating every publicly claimed issue as independently confirmed or resolved.