CVE-2025-8875 — N-able N-Central Insecure Deserialization Vulnerability

CVE-2025-8875

N-able N-Central RMM — Java Deserialization RCE; Paired with CVE-2025-8876 Command Injection; 7-Day Emergency Deadline

What is N-able N-Central?

N-able N-Central is a Remote Monitoring and Management (RMM) platform for Managed Service Providers (MSPs). See CVE-2025-8876 for the full MSP supply-chain context. CVE-2025-8875 and CVE-2025-8876 are companion vulnerabilities patched in the same N-Central 2025.3.1 emergency release.

Overview

CVE-2025-8875 is an insecure deserialization vulnerability (CWE-502) in N-able N-Central that allows an authenticated attacker with low-level access to achieve code execution on the N-Central server through deserialization of a maliciously crafted serialized object. N-Central is a Java-based platform — Java deserialization vulnerabilities in Java applications typically exploit gadget chains in bundled libraries (such as Apache Commons Collections) to achieve arbitrary code execution. The CVSS attack vector is Local (AV:L) rather than Network for this CVE — reflecting that the deserialization trigger may require local access or an inter-process channel rather than direct HTTP exploitation.

Affected Versions

Product Vulnerable Fixed
N-able N-Central < 2025.3.1 2025.3.1

Technical Details

The insecure deserialization (CWE-502) occurs in N-Central's Java application stack. N-Central uses Java serialization for internal data handling. When attacker-controlled serialized data is submitted to a vulnerable deserialization endpoint (accessible to authenticated low-privilege users), Java's native deserialization mechanism instantiates objects from the serialized data stream. By crafting a serialized payload using a deserialization gadget chain (a sequence of Java class instantiations that produces code execution as a side effect), the attacker achieves arbitrary code execution in the N-Central server process context.

Attack chain in MSP context: Once code execution is achieved on the N-Central server, the attacker has access to the RMM's legitimate remote management capabilities — enabling lateral movement to all managed client endpoints. This mirrors the chain for companion CVE-2025-8876 (command injection) — both CVEs lead to the same high-impact outcome from different technical mechanisms.

Chaining scenario:

  • CVE-2025-8875 (deserialization): initial RCE on N-Central server from low-privilege account
  • CVE-2025-8876 (command injection): persistence and privilege escalation

Discovery

Not publicly attributed.

Exploitation Context

CISA added CVE-2025-8875 to the KEV catalog simultaneously with CVE-2025-8876 on August 13, 2025, with the same 7-day emergency deadline. Both were actively exploited. The dual-CVE simultaneous listing suggests attackers chained both vulnerabilities in the same campaign or that both were independently discovered and exploited.

Remediation

  1. Upgrade N-Central to 2025.3.1 immediately. Both CVE-2025-8875 and CVE-2025-8876 are patched in this release. The CISA deadline was August 20, 2025.
  2. Enable MFA for all N-Central accounts — prevents credential-based initial access that would allow low-privilege authentication.
  3. Restrict N-Central access to known IP addresses; use VPN or IP allowlisting for all management access.
  4. Audit serialization endpoints — if the N-Central vendor provides guidance on disabling or restricting serialization endpoints, apply it.
  5. See CVE-2025-8876 for additional MSP-specific remediation guidance applicable to both CVEs.

Key Details

PropertyValue
CVE ID CVE-2025-8875
Vendor / Product N-able — N-Central
NVD Published2025-08-14
NVD Last Modified2025-10-27
CVSS 3.1 Score7.8
CVSS 3.1 VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
SeverityHIGH
CWE CWE-502 find similar ↗
CISA KEV Added2025-08-13
CISA KEV Deadline2025-08-20
Known Ransomware Use No

CVSS 3.1 Breakdown

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Required Action

CISA BOD 22-01 Deadline: 2025-08-20. Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Timeline

DateEvent
2025-08-13N-able releases N-Central 2025.3.1 with fix; CISA adds to KEV with 7-day emergency deadline
2025-08-14CVE published
2025-08-20CISA BOD 22-01 emergency remediation deadline (7 days)

References

ResourceType
N-able N-Central 2025.3.1 Release Announcement Vendor Advisory
NVD — CVE-2025-8875 Vulnerability Database
CISA KEV Catalog Entry US Government