Payments are experiencing issues due to temporary restrictions in Russia. If your payment does not go through, please submit a support request.Our support team is available 24/7 — we are always here to help with hosting and server issues.We are now accepting requests for dedicated server rental and colocation services in our data center.Reminder: we recommend enabling backups for additional data protection.A new VPS/VDS lineup with NVMe storage and improved performance is now available.Maintenance work on some servers has been completed. All services are operating normally.
Article4 min readViews3

N-central HF3 Released: Why Updating the Server Is Not Enough

N-able released a critical HF3 update. We examine the responsibilities of Hosted and On-Premises environments, updating all Agents and Probes, verifying connections, and remaining limitations.

Comments 0

A woman inspects one of three compact network devices on a light-colored desk.
In this article

On November 16, N-able released a critical update for N-central 2026.4 HF3, server build 2026.4.1.39. Administrators of this infrastructure management system must check not only the server: all clients, including Hosted, must update Agents and Probes to the version designated by the manufacturer as 2026.4.1 HF3. Unupdated components remain vulnerable to substitution.

This is critical for companies and contractors managing servers and workstations via N-central. Merely having a VPS, a Bitrix website, or corporate email does not imply dependency on this product: first, confirm with your administrator whether N-central is in use.

What's New in HF3

The update strengthens authentication and permission checks, file processing and imports, and the communication between Agents and Probes and the server. It includes HF2 fixes and permanently blocks the Legacy API; the setting to enable it has been removed. Check dependent integrations and agree on supported replacements; do not count on the old API being re-enabled after the update.

Previously, on November 13, N-able reported indicators of compromise for customers who had not disabled the Legacy API. The current trigger is an available fix with specific administrator responsibilities. The release date does not mean a new attack began on November 17 or that all customer devices have been updated.

Who Updates the Server and Who Updates the Devices

  • In a standalone On-Premises installation, the customer updates both the N-central server and all Agents and Probes.
  • In Hosted/NCOD, N-able updates the server. Updating Agents and Probes remains the customer's responsibility.
  • Previously updating these components to HF2 does not eliminate the need to upgrade to HF3.

For the server, the vendor lists supported source versions: 2025.4, 2026.1–2026.3, 2026.3.1 with HF1–HF4, as well as 2026.4 with HF1 or HF2, or without them. An older installation requires an intermediate upgrade. Verify your source build against the vendor's table and instructions before modifying the production system.

What to check after the update

Allow Agents time to reconnect, then open Configuration → Asset Discovery → Discovered Assets → Inactive Assets. The list populates as connections are established, so an initially empty tab does not confirm that the check is complete.

An inactive Agent alone does not prove an attack: standard reasons include cloning, reinstallation, and restoring the server from a backup. First, determine which device and installation the record belongs to. Do not activate all records sequentially: Set Active changes the active Agent for the device, rendering the previous one inactive. To connect, at least one identifier is now required—either the SMBIOS ID or the machine ID; if neither is present, the server rejects the connection.

What limitations remain

Intune remains blocked. Other remote management functions, except Take Control, are disabled; Take Control continues to work. Therefore, installing HF3 does not mean all previous capabilities are restored.

If your Agents and Probes have not yet been updated to HF2, consider its separate compatibility rules. HF2 changed the Agent–Probe connection, whereas HF3 strengthens their connection to the server. The HF2 instructions specify an order of Agents, then Probes; prematurely updating a Probe can temporarily disrupt dependent functions, including offline patch caching. The updated PME is delivered automatically. Check component compatibility via documentation, not just the server build number.

The verification result includes confirmed versions of the server and all managed components, restored connections, and resolved inactive records. If signs of prior interference are present, save logs before cleanup and conduct a separate investigation: installing the patch does not automatically remove the consequences of a compromise.

Information verified on November 17, 2026, at 09:05 MSK. HF3 was published on November 16; the exact release time is not specified in the notes.

Discussion 0

Share your experience and ask questions. Comments without links appear after editorial review.

No comments yet. Start the discussion.