CVE-2026-129281 in N-central
Summary
by MITRE • 11/17/2026
N-able N-central before 2026.4.1 HF3 checks only a view permission for ServerII2 operations that write device execution configuration. An authenticated user with view-only access to a device can set configuration that the Windows agent on that device acts on.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 11/17/2026
The vulnerability identified in N-able N-central prior to version 2026.4.1 Hotfix 3 represents a critical authorization bypass within the platform's server-side logic, specifically affecting operations related to ServerII2 configurations. This flaw stems from an insufficient access control mechanism where the system fails to enforce proper privilege checks for actions that modify device execution settings. Instead of verifying whether the authenticated user possesses write or administrative permissions required to alter configuration states, the application only validates if the user has view-only permission on the target device. This logical error allows any authenticated account with read access to perform state-changing operations that should be restricted to administrators or users with explicit modification rights.
From a technical perspective, this vulnerability enables an attacker who has obtained valid credentials for a low-privilege account to manipulate the configuration of managed endpoints through the N-central interface. The Windows agent deployed on these devices is designed to act upon configurations pushed by the central management server without performing its own secondary authorization checks against the user's privilege level. Consequently, when a view-only user submits a request to change device execution parameters, the ServerII2 component processes this request and propagates it to the endpoint agents. This creates a direct path for unauthorized configuration changes that can alter how software executes on managed systems, potentially disabling security controls or enabling malicious behaviors under the guise of legitimate administrative tasks.
The operational impact of this vulnerability is significant as it undermines the principle of least privilege within the N-able ecosystem. An attacker with view access could theoretically disable endpoint protection agents, modify firewall rules, change startup configurations, or execute arbitrary commands depending on what specific configuration parameters are exposed through the ServerII2 interface. This level of control effectively grants an unprivileged user administrative capabilities over managed devices, facilitating lateral movement within a network if those endpoints have broader connectivity privileges. It also poses a risk to system integrity and availability, as malicious actors could destabilize critical infrastructure by applying incorrect or destructive configurations that disrupt normal operations.
This issue aligns with CWE-269, which describes Improper Privilege Assignment, where the software does not assign appropriate privileges for specific security-relevant functions. Furthermore, it relates to ATT&CK technique T1078, Valid Accounts, as exploitation relies on existing credentials, and potentially T1546, Event Triggered Execution or T1222, File and Directory Permissions Modification, depending on the exact nature of the configuration changes allowed. The vulnerability highlights a common pitfall in web application development where backend logic assumes that view permissions imply no risk for certain operations, failing to distinguish between data retrieval actions and state-modifying actions.
Mitigation strategies should prioritize immediate patching by upgrading N-able N-central to version 2026.4.1 Hotfix 3 or later, which resolves the authorization check flaw in ServerII2. In environments where patching is not immediately feasible, network segmentation can help limit access to the management interface from untrusted networks. Additionally, organizations should review their role-based access control policies within N-able to ensure that view-only permissions are strictly limited to monitoring and reporting functions without any ability to trigger configuration updates. Implementing multi-factor authentication for all administrative accounts adds a layer of defense against credential theft, while continuous monitoring of audit logs can help detect unauthorized attempts to modify device configurations by low-privilege users.