basicsecurity.net
Proof, not just disclosure.
Threats / N-able / CVE-2025-8875
CVE-2025-8875 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-133EPSS 0.01582 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported 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).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.01582 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: N-able, N-Central. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 7 reported-exploitation source(s)
  • Catalogued by N-able (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by N-ableCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.