CVE Intelligence
CISA KEV High Injection

CVE-2025-8876 — N-able N-Central Command Injection Vulnerability

Improper Input Validation vulnerability in N-able N-central allows OS Command Injection.This issue affects N-central: before 2025.3.1.

Published Aug 14, 2025 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories, NIST National Vulnerability Database · CNA: N-able

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Aug 13, 2025
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • EPSS 3.4% (30-day exploitation probability)+13
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Aug 13, 2025
EPSS FIRST
3.45%
ahead of 89% of scored CVEs · Oct 14, 2026
Affects
N-able
N-central
CVSS base
8.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

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

US federal deadline: Aug 20, 2025 — passed 421 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (N-able N-central).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  4. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
N-able N-central < 2025.3.1 Vulnerable CVE Program (cve.org) e CISA ADP
N-able N-central < 2025.3.1 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.4 CVSS 4.0 Critical — — a5532a13-c4dd-4202-bef1-e0b8f2f8d12b via NIST National Vulnerability Database
9.4 CVSS 4.0 Critical — — N-able via CVE Program (cve.org) e CISA ADP
8.8 CVSS 3.1 High 2.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
8.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-78 · OS Command Injection

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Aug 13, 2025
Federal deadline
Aug 20, 2025
passed 421 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 3.45%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
  • Hunt retroactively in logs from before Aug 13, 2025 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · n-able/n-central
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.4 → 8.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 13, 2026
  • Affected products added · n-able/n-central
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 9.4
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2025
  • CVE published
    Aug 14, 2025 · N-able
  • Added to CISA KEV catalog
    Aug 12, 2025 · CISA

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

5 on the record

Elsewhere on this site

N-able
every CVE for this vendor
2025-08
what else CISA listed that month
Injection
same class
CWE-78
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-86218 N-able N-central Static Code Injection Vulnerability KEV Sep 6, 2026
  • CVE-2026-18577 N-able N-central Authentication Bypass Using an Alternate Path or Channel Vulnerability KEV Aug 2, 2026
  • CVE-2026-18556 N-able N-central Authentication Bypass Using an Alternate Path or Channel Vulnerability KEV Aug 1, 2026
  • CVE-2025-9316 N-central unauthenticated sessionID generation Nov 12, 2025
  • CVE-2025-11366 N-central Authentication bypass via path traversal Nov 12, 2025
  • CVE-2025-11367 N-central windows software probe Remote Code Execution Nov 12, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-8876 is "N-able N-Central Command Injection Vulnerability", rated High. It affects N-central (N-able); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 3.45% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.