N-able Releases Critical N-central Security Update Fixing 17 Vulnerabilities
N-able has released a critical security update for its N-central Remote Monitoring and Management (RMM) and Unified Endpoint Management (UEM) platform, addressing 17 security vulnerabilities affecting authentication, access controls, file handling, server components, and user management.
The update, N-central 2026.4 Hotfix 3 (HF3), builds on security protections introduced in Hotfix 2 (HF2) and introduces additional safeguards across the platform.
According to N-able, the latest release strengthens authentication and access controls, Agent and Probe communications, appliance security, file and import handling, server components, legacy APIs, and user management.
One significant change is the complete removal of the legacy API configuration option, permanently blocking access to these older interfaces.
What Does N-central Hotfix 3 Fix?
N-able has implemented security improvements across several areas of the platform:
- Authentication and access controls: Strengthened authentication mechanisms and authorization checks.
- Agent, Probe, and appliance security: Improved communication security and protection against impersonation.
- File and import handling: Addressed vulnerabilities involving XML processing, file operations, and imported data.
- Server hardening: Fixed weaknesses affecting server components and legacy interfaces.
- User management: Improved controls to prevent unauthorized access and privilege misuse.
At the time of the announcement, N-able also noted that Remote Control functionality and Intune integration remained blocked.
List of 17 Vulnerabilities Addressed
The N-central 2026.4 HF3 update addresses the following vulnerabilities:
CVE IDVulnerabilityCVE-2026-129271N-central Patch Management Local Privilege EscalationCVE-2026-129272MMS3 appliance authentication bypass via predictable passcodeCVE-2026-129273Audit Export syslog injection allowing root command executionCVE-2026-129274ServerMMS2 task result submission missing authenticationCVE-2026-129275repositoryItemGet missing authentication disclosing policiesCVE-2026-129276ServerMMS2 asset data submission missing authenticationCVE-2026-129277ServerMMS maintenance action read missing authenticationCVE-2026-129278Take Control audit log tampering without authenticationCVE-2026-129279Password reset response discrepancy allowing user enumerationCVE-2026-129280ServerUI SOAP operations missing authorization checksCVE-2026-129281View-only users can set DeviceExecute configurationCVE-2026-129282Test email sendmail argument injection due to missing authorizationCVE-2026-129283N-central custom service import XML external entity injectionCVE-2026-129284Report Manager and Data Export settings SSRFCVE-2026-129285XMPP action response origin validation errorCVE-2026-129286SIS GenericFiles version path traversal leading to RCECVE-2026-129287SIS repository parser XML external entity injection
Several of these vulnerabilities involve missing authentication or authorization checks, potentially allowing unauthorized users to access sensitive operations and information. Others involve privilege escalation, command execution, server-side request forgery (SSRF), path traversal, and XML external entity (XXE) injection.
Update Follows Active Exploitation of Earlier N-central Vulnerabilities
The latest security release comes days after N-able restricted certain N-central features and integrations following the disclosure of another set of vulnerabilities tracked as 4EverAble2Shell and Agent2Shell.
These earlier vulnerabilities could allow attackers to execute arbitrary code with root privileges and obtain SYSTEM-level access to Windows systems under specific conditions.
Exploitation of 4EverAble2Shell depends on legacy API mode being enabled. By removing the legacy API configuration option in the latest N-central release, N-able has closed this particular attack vector.
The earlier vulnerabilities have also reportedly come under active exploitation. Attackers were observed leveraging them to deploy cryptocurrency miners on vulnerable servers.
Independent security researcher Sean Bales, who disclosed the vulnerabilities, has also published additional technical details covering 24 CVEs. He noted that these are patched vulnerabilities and should not work against systems running the latest security update.
What N-able Customers Should Do
N-able has issued different upgrade instructions depending on how customers deploy N-central.
For on-premises customers:
- Upgrade N-central servers to version 2026.4 Hotfix 3 as soon as possible.
- Verify that the latest security patches have been successfully applied.
- Upgrade all connected Agents and Probes to their latest versions.
- Review authentication and access-control configurations.
- Confirm that legacy API functionality is no longer available.
For hosted N-central customers:
N-able says no server-side action is required because the security updates are being applied automatically.
However, hosted customers must still upgrade all Agents and Probes to the latest versions.
N-able specifically warned that outdated Agents and Probes remain susceptible to impersonation attacks.
The company emphasized that all customers, including hosted and on-premises deployments, must update their Agents and Probes to receive full protection.
Conclusion
The release of N-central 2026.4 Hotfix 3 addresses 17 vulnerabilities affecting important components of N-able's RMM and UEM platform.
The removal of legacy APIs is particularly significant because it eliminates the attack path associated with the earlier 4EverAble2Shell vulnerability. However, organizations must not overlook the requirement to update connected Agents and Probes.
Administrators should prioritize the upgrade, verify that all connected components are running supported versions, and review their environments for signs of suspicious activity associated with the earlier N-central vulnerabilities.