CVE-2025-7051: N-able N-central · Improper Access Control
Affects N-able N-centralSource CVE Database V5
Not known to be exploited · CVSS 8.3 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| N-able N-central | Affected
| Fixed in– |
AI-suggested
- Upgrade N-able N-central to version 2025.2 or later as soon as the patch is released to remediate the vulnerability.
- Until patching is possible, restrict authenticated user access strictly to trusted personnel and enforce the principle of least privilege, minimizing the number of users with syslog configuration permissions.
- Implement network segmentation and access controls to limit exposure of the N-central management interface to only authorized IP addresses and VPNs.
- Monitor syslog configuration changes and audit logs regularly for unauthorized modifications or suspicious activities.
- Use multi-factor authentication (MFA) for all users accessing N-central to reduce the risk of compromised credentials.
- Consider deploying additional logging and alerting mechanisms external to N-central to detect anomalies in log management.
- Engage with N-able support and subscribe to security advisories to stay informed about updates and best practices.
Description
On N-central, it is possible for any authenticated user to read, write and modify syslog configuration across customers on an N-central server. This vulnerability is present in all deployments of N-central prior to 2025.2.