CVE-2026-86218
N-Able N-Central ≤ 2026.3
Raw vector
CVSS: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:XCVSS 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
- 🇪🇺 ENISA EUVD: EUVD-2026-72041
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
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
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.
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.
Security testing in development and acceptance will detect static code injection but does not prevent it at the source.
Secure coding explicitly requires proper neutralization of directives in templates, libraries and configuration files.
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.