CVE-2025-8875
CVE-2025-8875 is a critical-severity vulnerability (CVSS 4.0 CVSS-B score 9.4). N-able N-Central contains an insecure deserialization vulnerability that could lead to command execution. CISA added it to the Known Exploited Vulnerabilities catalog on 2025-08-13, with a remediation due date of 2025-08-20 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 2.4% probability of exploitation in the next 30 days, in the 84th percentile of scored CVEs.
Updated
- CVSS 4.0
- 9.4 CRITICAL
- EPSS
- 2.4% (84th pct)
- CISA KEV
- Exploited
- Published
- 2025-08-14
- Weakness
- CWE-502
N-able N-Central Insecure Deserialization Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
https://status.n-able.com/2025/08/13/announcing-the-ga-of-n-central-2025-3-1/ ; https://nvd.nist.gov/vuln/detail/CVE-2025-8875
Description
Deserialization of Untrusted Data vulnerability in N-able N-central allows Local Execution of Code.This issue affects N-central: before 2025.3.1.
Key Findings
as of 2026-11-22- CISA added CVE-2025-8875 to the KEV catalog 1 day before its CVE record was published. The CNA dates the vulnerability's public disclosure to 2025-08-13, the day it was added. The median for entries added in 2025 is 26 days.
- It is one of 5 N-able entries in the CISA KEV catalog, and one of 2 added in 2025.
- Its current EPSS score (2.4%) is higher than that of 8% of CISA KEV entries.
Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2025-08-14).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| N-able | N-able N-central | 0 to <2025.3.1 |
References
1 linksRecord Details
- Publicly disclosed
- 2025-08-13
- Published
- 2025-08-14
- Last updated
- 2025-10-21
- Assigner (CNA)
- N-able
- Credited to
- -
More from N-able
Unauthenticated administrative account takeover
pre-authentication remote code execution
Incomplete patch leads to administrative account takeover
Command Injection Vulnerability
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.