Threats / N-able / CVE-2025-8875
CVE-2025-8875
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
N-able N-Central vulnerability
N-able N-Central contains an insecure deserialization vulnerability enabling remote command execution. The flaw has been exploited in the wild.
Verdict
Today item — known-exploited.
Insecure deserialization in N-Central allows unauthenticated or low-privileged attackers to execute arbitrary commands on affected systems. Active exploitation in the wild elevates risk for organizations using this remote management platform.
CISA KEV Yes · 2025-08-135EPSS 0.01588 (verify live)6CVSS 9.43CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-08-13).
Probability (EPSS)
EPSS 0.01588 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 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) · Affected: N-able, N-Central. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
Weakness (CWE)
Mapped to CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious serialized object and send it to the N-Central service endpoint.
Business
Attackers gain code execution within the N-Central application context, potentially compromising the management platform itself.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary commands on the N-Central server to establish persistence or move laterally.
Business
The organization loses control of its remote management infrastructure, exposing all monitored endpoints to compromise.
3
Lateral reach — past segmentation narrative 3
Attacker
I pivot from N-Central to customer endpoints under management to deploy malware or steal data.
Business
Customers of N-Central users face secondary compromise, creating cascading liability and reputational damage.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05