CVE-2026-129287 in N-central
Summary
by MITRE • 11/17/2026
N-able N-central before 2026.4.1 HF3 processes XML external entities in software repository files. An attacker able to supply or modify the repository files received by the server can read files accessible to the N-central service account or cause the server to make outbound requests.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Analysis
by VulDB Data Team • 11/17/2026
The vulnerability identified within N-able N-central versions prior to 2026.4.1 HF3 constitutes a critical XML External Entity injection flaw, specifically categorized under CWE-611 in industry standard classification systems. This security defect arises from the application's failure to properly validate or restrict the processing of external entities when parsing XML data contained within software repository files. In modern enterprise environments, N-central serves as a centralized platform for managing IT infrastructure, and its reliance on XML-based configuration and repository structures creates an attack surface that is exploitable if input sanitization controls are insufficiently rigorous against entity expansion techniques.
The technical mechanism of this vulnerability allows an attacker who possesses the ability to supply or modify the software repository files received by the N-central server to inject malicious external entity definitions into the XML payload. When the application processes these modified files, it interprets the injected entities and resolves them according to the underlying XML parser's default behavior. This process enables two primary vectors of exploitation: local file disclosure and Server-Side Request Forgery. By crafting specific entity references that point to internal system paths, an attacker can force the server to read arbitrary files from the host operating system. The scope of this data exposure is limited by the privileges assigned to the N-central service account, meaning any file readable by that user context becomes accessible through successful exploitation.
Beyond local information disclosure, the vulnerability facilitates outbound network requests initiated by the vulnerable application itself. This capability aligns with the Server-Side Request Forgery (SSRF) technique documented in the MITRE ATT&CK framework under identifier T1589. Through this mechanism, an attacker can direct the N-central server to connect to internal or external resources that would otherwise be inaccessible from the public internet. This not only allows for further reconnaissance of the internal network topology but also enables interaction with backend services, such as cloud metadata endpoints or internal API servers, potentially leading to broader compromise if those downstream systems have weaker security postures.
The operational impact of this vulnerability is significant due to its potential role in a larger attack chain. Initial access through repository file manipulation can lead to the exfiltration of sensitive configuration data, credentials stored within accessible files, or proprietary intellectual property hosted on the server. Furthermore, the ability to make outbound requests transforms the N-central instance into a pivot point for lateral movement within the network. Attackers may leverage this capability to probe internal services, exploit other vulnerabilities in connected systems, or establish persistent backdoors by downloading additional malicious payloads from external command and control servers.
Mitigation strategies must focus on immediate patching and architectural hardening. The primary remediation is to upgrade N-able N-central to version 2026.4.1 HF3 or later, where the vendor has implemented fixes for this XML parsing issue. In environments where immediate patching is not feasible, administrators should enforce strict file integrity monitoring on software repository directories to detect unauthorized modifications. Additionally, network segmentation and egress filtering can mitigate the impact of outbound request capabilities by restricting the N-central service account's ability to initiate connections to untrusted external domains or sensitive internal subnets. Input validation controls that explicitly disable DTD processing and external entity resolution in XML parsers should also be verified as active within the application configuration to prevent similar exploitation vectors across other modules.