# CVE-2025-8875: N-able N-Central Insecure Deserialization

> An insecure deserialization flaw in N-able N-central allows local attackers to execute arbitrary code, requiring an upgrade to the latest version.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Yes, since 13 Aug 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2025
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-rhqj-c64h-w74r

## What is CVE-2025-8875?

CVE-2025-8875 is a critical unsafe deserialization vulnerability in N-able N-central, published on 14 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2025-8875?

It affects 1 product.


Products: N-Able N-Central.

## How do I fix CVE-2025-8875?

No fix has been published for CVE-2025-8875 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 20 Aug 2025.

## Is CVE-2025-8875 being exploited?

Yes. Attackers have exploited CVE-2025-8875 in the wild since at least 13 Aug 2025.

Public exploit code:

- Detection for CVE-2025-8875 & CVE-2025-8876 (github_poc): https://github.com/rxerium/CVE-2025-8875-CVE-2025-8876

## Other vulnerabilities in N-able N-central

- [CVE-2026-86218](https://insights.sbomify.com/CVE-2026-86218/): N-able N-central Static Code Injection (critical 10.0, exploited in the wild)
- [CVE-2025-8876](https://insights.sbomify.com/CVE-2025-8876/): N-able N-Central Command Injection (critical 9.4, exploited in the wild)
- [CVE-2026-18577](https://insights.sbomify.com/CVE-2026-18577/): N-able N-central Authentication Bypass Using an Alternate Path or Channel (high 8.2, exploited in the wild)
- [CVE-2026-18556](https://insights.sbomify.com/CVE-2026-18556/): N-able N-central Authentication Bypass Using an Alternate Path or Channel (high 8.2, exploited in the wild)
- [CVE-2025-11367](https://insights.sbomify.com/CVE-2025-11367/): N-central windows software probe Remote Code Execution (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8875 and fix it if it is affected.

What it is: CVE-2025-8875 is a critical unsafe deserialization vulnerability in N-able N-central, published on 14 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-8875 in the wild since at least 13 Aug 2025.

Affected product: N-able N-central. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8875/ (Markdown: https://insights.sbomify.com/CVE-2025-8875/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8875
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8875
- OSV: https://osv.dev/vulnerability/CVE-2025-8875

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8875/
Summaries are generated and may contain mistakes; the official description above is the record.