← All articles

N-central vulnerabilities: 17 flaws fixed in critical update

N-central vulnerabilities: 17 flaws fixed in critical update

N-central vulnerabilities are the focus of a critical security update that fixes 17 flaws in N-able’s remote management platform. The update, N-central 2026.4 Hotfix 3, strengthens the Remote Monitoring and Management (RMM) and Unified Endpoint Management (UEM) system, which administrators use to monitor and manage devices.

N-able says the hotfix adds to protections introduced in Hotfix 2. The changes cover login and access controls, communications between the platform and its Agents and Probes, file and import processing, server components, older application programming interfaces (APIs), and user management. An API is a way for software components to communicate with each other.

The update also removes the configuration option for legacy APIs completely. That permanently blocks those older interfaces. This change matters because a separate group of flaws known as 4EverAble2Shell depended on legacy API mode being enabled. Removing the mode closes that particular route in the latest N-central version.

N-able says some features and integrations are currently blocked, including Remote control functionality and Intune integration. Customers running N-central on their own premises should upgrade their servers as soon as possible. Hosted N-central customers do not need to take server-side action because those updates are applied automatically.

There is still an important step for every customer. N-able says all Agents and Probes, including those used with hosted deployments, must be upgraded to the latest version for full protection. An Agent is the software installed on a managed device, while a Probe is a component that helps N-central communicate with and monitor systems. N-able warns that outdated Agents and Probes are vulnerable to impersonation, meaning an attacker may be able to make a malicious system appear legitimate.

The 17 vulnerabilities cover several types of security weakness. They include a local privilege escalation flaw in patch management, an authentication bypass in the MMS3 appliance caused by a predictable passcode, and an audit export issue that could allow root command execution through syslog injection. Root is the highest level of control on many Unix-like systems. Other flaws involve missing authentication when submitting task results or asset data, exposing policies, reading maintenance actions, and altering Take Control audit logs.

The list also includes a password-reset response discrepancy that allows user enumeration, missing authorisation checks in ServerUI SOAP operations, and a privilege issue allowing view-only users to set DeviceExecute configuration. Further vulnerabilities affect test email sendmail arguments, custom service import XML processing, Report Manager and Data Export settings, XMPP action response origin validation, and SIS file handling. XML external entity injection can make an application process hostile instructions hidden in XML data. Server-side request forgery, or SSRF, can make a server send requests it was not meant to send. Path traversal can let an attacker reach files outside an intended directory, and remote code execution, or RCE, means running commands on a target system.

The update follows restrictions introduced days earlier after the disclosure of 4EverAble2Shell and Agent2Shell. Under specific conditions, those flaws could let attackers run arbitrary code as root and obtain SYSTEM-level access to Windows systems. SYSTEM is a highly privileged Windows account. The 4EverAble2Shell route specifically required legacy API mode, which is why its removal from the newest N-central version is a central mitigation.

Those earlier vulnerabilities are not only theoretical. They have been actively exploited, with attackers using them to deploy cryptocurrency miners on vulnerable servers. A cryptocurrency miner consumes computing resources to generate digital currency, which can burden affected systems and their administrators. An independent security researcher who disclosed the flaws has also published details for 24 CVEs, stating that the patched vulnerabilities should not work against the latest patch.

Administrators should therefore treat the server update and the Agent and Probe upgrades as separate tasks. On-premise customers need to update their N-central servers, while hosted customers should verify that every connected Agent and Probe has been upgraded. For organisations that need broader help with security-focused IT infrastructure and consulting, AEU-I describes its service as security-first IT, infrastructure and consulting.

Also available in: DeutschItalianoShqip