N-able N-central EUVD-2026-72022

Exploitation requires the attacker to hold at minimum a low-privilege authenticated session in the target N-central instance (PR:L in CVSS 4.0). Network-level access to the N-central server is also required (AV:N). The AT:P (Attack Requirements: Present) metric indicates a specific precondition - likely related to session state, a particular API request structure, or endpoint reachability - must be satisfied, though the vendor advisory does not publicly detail the exact trigger. Exploitation is limited to N-central versions strictly earlier than 2026.3 HF 3. Unauthenticated remote attackers without any N-central account cannot exploit this vulnerability. MSPs with strict least-privilege account management and IP-restricted access to the N-central console have a meaningfully lower exploitable attack surface.

The CVSS 4.0 score of 7.7 with VC:H/VI:H/VA:H on the vulnerable system signals high potential impact if the bypass is successfully triggered. The PR:L metric confirms this is not unauthenticated - an attacker must first have a valid low-privilege account in N-central, which meaningfully limits opportunistic exploitation from the public internet. AT:P further constrains exploitation by requiring specific conditions, reducing automated mass exploitation risk. EPSS data is not provided; given the narrow prerequisite (authenticated low-priv account), real-world exploitation probability should be lower than raw CVSS impact metrics suggest. The most critical risk amplifier is N-central's role as an MSP hub: a single compromised N-central instance may manage hundreds of customer environments, so privilege escalation to internal APIs could provide lateral movement vectors far beyond the N-central platform itself. No KEV listing or public exploit code is known at time of analysis.

An attacker who has obtained or created a low-privilege account in an N-central instance - for example, a disgruntled MSP employee, a compromised technician credential, or a trial account - crafts requests to internal-only API endpoints that would normally be restricted to privileged backend services. By exploiting the authentication bypass, the attacker accesses these APIs without the expected privilege checks, potentially reading sensitive managed-device telemetry, escalating their own role, or issuing commands to managed endpoints across customer tenants. No public exploit code is known, so exploitation currently requires knowledge of the specific internal API paths and the bypass technique.