dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 20 Aug 2025.
N CentralApplication · N Able

CVE-2025-8875

HIGH · 7.8 CVSS v3.1 Published 2025-08-14
Fix available
A fix is available. Upgrade to 2025.3.1 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Deserialization of Untrusted Data vulnerability in N-able N-central allows Local Execution of Code.This issue affects N-central: before 2025.3.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A deserialization vulnerability in N-able N-central prior to version 2025.3.1 allows an attacker with local access to execute arbitrary code through unsafe deserialization of untrusted data. This is a code-execution vulnerability in the backup/import functionality where malicious serialized objects can trigger dangerous code paths during reconstruction.

MitigationUpgrade N-able N-central to version 2025.3.1 or later to obtain the vendor patch. If immediate patching is not feasible, restrict local access to the N-central server and monitor for unauthorized access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
N CentralApplication
Affected:< 2025.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm N-able N-central is present
    Identify if N-able N-central server software is installed in your environment. Look for the n-central service, related processes, or installation directories on the system.
    Affected if N-able N-central software is found in your environment
  2. Retrieve installed version number
    Locate the version of N-able N-central. This is typically accessible via the software's About section in the management interface, a version file on the server, or the service information displayed in the control panel.
    Affected if You cannot determine the version or find it is below 2025.3.1
  3. Compare version against vulnerability threshold
    Compare your installed version to the affected range: any version prior to 2025.3.1. The vendor fixed this vulnerability in version 2025.3.1.
    Affected if The installed version is lower than 2025.3.1

Your environment is affected if N-able N-central is installed and running any version below 2025.3.1, since the vulnerability allows code execution by an authenticated attacker via unsafe deserialization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2025.3.1 or later
Fixed in 2025.3.1
Interim mitigation

Upgrade N-able N-central to version 2025.3.1 or later to obtain the vendor patch. If immediate patching is not feasible, restrict local access to the N-central server and monitor for unauthorized access attempts.

Recommended fix High confidence

2025.3.1

  1. Ensure you have a complete backup of your N-central installation and database before beginning the upgrade process
  2. Review the official N-able N-central 2025.3.1 release notes for any specific upgrade prerequisites or procedures
  3. Download the N-central 2025.3.1 update from the official N-able portal or appropriate distribution channel
  4. Stop all N-central services according to the documented shutdown procedure
  5. Install the 2025.3.1 upgrade following the standard N-central upgrade documentation
  6. Verify all services start successfully after the upgrade
  7. Confirm the N-central version displays as 2025.3.1 in the administration console
  8. Validate that critical monitoring and functionality are operating normally
Caveat Review N-able release notes for any configuration or feature changes between your current version and 2025.3.1

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in N Central Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,840
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8875 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8875 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data