Security Resilience

CVE-2026-86218

N-Able N-Central ≤ 2026.3

CISA KEVActive ExploitationEUVD Exploited
Published
06 September 2026
Modified
09 September 2026
KEV Added
08 September 2026
Patch / advisory
CVSS Score v4 10.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.15 97th percentile
Risk Priority 75 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-86218 is a critical-severity Static Code Injection (CWE-96) vulnerability in N-Able N-Central. Its CVSS base score is 10.0 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 3% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

N-central is vulnerable to a pre-auth remote code execution This issue affects N-central: before 2026.3.1.14.

CWE(s)
KEV Date Added
08 September 2026

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1137 Office Application Startup Persistence
Adversaries may leverage Microsoft Office-based applications for persistence between startups.
T1137.004 Outlook Home Page Persistence
Adversaries may abuse Microsoft Outlook's Home Page feature to obtain persistence on a compromised system.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1505 Server Software Component Persistence
Adversaries may abuse legitimate extensible development features of servers to establish persistent access to systems.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-8875Same product: N-Able N-Centralboth on KEV
CVE-2026-18556Same product: N-Able N-Centralboth on KEV
CVE-2025-8876Same product: N-Able N-Centralboth on KEV
CVE-2026-18577Same product: N-Able N-Centralboth on KEV
CVE-2025-11367Same product: N-Able N-Central
CVE-2025-11366Same product: N-Able N-Central
CVE-2025-10231Same product: N-Able N-Central
CVE-2024-8510Same product: N-Able N-Central
CVE-2024-28200Same product: N-Able N-Central
CVE-2025-11700Same product: N-Able N-Central

Affected Assets

n-able
n-central
2026.3 · ≤ 2026.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation can discover missing neutralization of directives in saved code artifacts.

Input validation directly stops unneutralized directives from being inserted into static code resources.

Engineering principles include secure input handling and neutralization requirements that structurally avoid static injection.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly require input neutralization to block static code injection into templates, configs, or libraries.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development and acceptance will detect static code injection but does not prevent it at the source.

prevents

Secure coding explicitly requires proper neutralization of directives in templates, libraries and configuration files.

finds

A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw. CWE-96 is a first-party code defect (user input written into an executable resource), and while some instances surface as CVEs (the observed examples include CVE-2002-0495, CVE-2005-1876, etc.), the vast majority of static code injection in deployed code is in custom applications that never get a published advisory. A.8.8 finds the disclosed minority; the source-reading and dynamic-testing routes that would reach the rest belong to A.8.29, not A.8.8.

References