CVE Alert: CVE-2025-8875 – N-able – N-central

CVE-2025-8875

UnknownCISA KEVExploitation active

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

CVSS v3.1 not provided
Vendor
N-able
Product
N-central
Versions
0 lt 2025.3.1
CWE
CWE-502, CWE-502 Deserialization of Untrusted Data
Vector
n a
Published
2025-08-14T14:56:11.884Z
Updated
2025-08-14T20:39:27.823Z

AI Summary Analysis

Risk verdict

Critical risk with active exploitation; treat as priority 1 and act now.

Why this matters

Deserialization of untrusted data enables remote code execution on a highly privileged management appliance, potentially giving an attacker full control over MSP or enterprise networks. The impact is broad: data exposure, integrity loss, and ability to pivot to connected systems.

Most likely attack path

An attacker remotely delivers a crafted payload over the network to the vulnerable component; no user interaction is required. Successful deserialisation yields code execution with low privileges, but the changed scope indicates high potential impact on the host and adjacent resources, enabling rapid uplift to broader access.

Who is most exposed

MSPs and organisations running N-central on-premises or in hosted deployments with direct or semi-direct exposure to management interfaces are at risk, especially where internet-facing access or lax network segmentation exists.

Detection ideas

  • Deserialization errors or unusual stack traces in application logs.
  • Unexpected process spawns or new child processes from the N-central service.
  • Anomalous outbound connections from the server to external hosts.
  • Creation of new services/tasks or unusual credential usage on the control server.
  • Sudden privilege escalations or unusual access patterns to management data.

Mitigation and prioritisation

  • Apply the latest patch (2025.3.1 or later) immediately; verify in staging before production rollout.
  • If patching is delayed, restrict exposure: segment the N-central host, block external access to management interfaces, force MFA, and enable allowlisting.
  • Implement compensating controls: WAF/reverse proxy, strict input validation, and monitor for deserialization-related indicators.
  • Ensure backups and recovery plans are up to date; test restoration.
  • Treat as priority 1 due to KEV presence and active exploitation.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below

To keep up to date follow us on the below channels.