CVE-2025-8875
Deserialization of Untrusted Data vulnerability in N-able N-central allows Local Execution of Code.This issue affects N-central: before 2025.3.1.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: allow-list classes · patch
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-8875 being exploited?
Yes. CVE-2025-8875 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-8875?
CVE-2025-8875 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-8875?
Yes. A fix has been recorded for CVE-2025-8875. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-8875 affect?
CVE-2025-8875 affects n-able:n-central. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected< 2025.3.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 14 Aug 2025 (SSVC 2.0.3).
timeline
- 13 Aug 2025Added to CISA KEV (exploited in the wild)
- 14 Aug 2025Published · 2 days later
- 14 Aug 2025CISA SSVC assessment: exploitation active · same day later
- 17 Aug 2025First proof-of-concept repository on GitHub (unvetted) · 2 days later
- 20 Aug 2025CISA remediation due date (US federal agencies) · 3 days later
- 21 Oct 2025CVE record last updated · 63 days (about 2 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Linkstatus.n-able.com /2025/08/13/announcing-the-ga-of-n-central-2025-3-1/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-8875
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.