CVE-2026-86218
N-able N-central Static Code Injection Vulnerability
Description
CVE-2026-86218 is a critical pre-authentication remote code execution vulnerability in N-able N-central, the remote monitoring and management platform used by managed service providers to administer customer endpoints. The flaw is classified as static code injection, in which attacker-supplied input is written to a location that is later parsed and executed as code, so an unauthenticated attacker who can reach the N-central web interface can execute arbitrary code on the server. N-central versions before 2026.3.1.14 are affected. Because a compromised N-central server controls every managed agent beneath it, this remote code execution vulnerability is a supply-chain risk for all of an MSP's customers; CVE-2026-86218 carries a CVSS score of 9.8 and is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
KEV Information
CVSS Score
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HOpen in CalculatorCWEs
Affected Products
| Vendor | Product | Version |
|---|---|---|
| n-able | n-central | < 2026.3; 2026.3 |
References
Weakness Type
CWE-96: Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')
Static code injection occurs when software takes input from an upstream component, stores it in a file or location that will later be parsed and executed as code, and fails to neutralise the code directives it contains. In CVE-2026-86218 unauthenticated input reaches such a persisted, later-interpreted location in N-central without neutralisation, so the attacker's directives are executed by the server the next time that content is processed — which is why the flaw yields pre-authentication remote code execution rather than mere data corruption.
Learn more: CWE-96 — Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')
Impact Analysis
CVE-2026-86218 is remotely exploitable over the network with low attack complexity, no authentication and no user interaction, so anyone able to reach the N-central interface can attempt it — and N-central servers are routinely internet-facing because agents must check in from customer networks. The impact is high across confidentiality, integrity and availability: code execution on the N-central server exposes stored credentials, customer inventories and agent communication secrets, allows the attacker to push commands or software to every managed endpoint, and permits the management platform to be disabled outright. For a managed service provider that is the worst possible blast radius, since a single compromised server converts into simultaneous access to many independent customer environments. The CVSS 3.1 base score of 9.8 (Critical) captures the technical severity, while the EPSS score of roughly 0.7% (53rd percentile) understates the real risk — CISA has confirmed active exploitation via its KEV listing, with a remediation deadline of 11 September 2026 that has already passed.
Exploit Maturity
CISA has confirmed active exploitation of CVE-2026-86218 by adding it to the Known Exploited Vulnerabilities catalog with a remediation deadline of 11 September 2026, which has already passed — exposed N-central servers should be considered targeted. No public exploit code appears among the available references; N-able's security advisory is the only technical source, which is common for RMM vulnerabilities where vendors deliberately withhold detail because the installed base includes many internet-facing servers. The EPSS score of about 0.7% (53rd percentile) is a weak indicator here, as it has not yet caught up with the confirmed in-the-wild activity. Remote monitoring and management platforms are a favoured target for ransomware affiliates precisely because they provide fan-out to many endpoints, so any N-central instance that was exposed while unpatched warrants a compromise assessment rather than a patch alone.
Remediation
- Follow the CISA KEV required action. Apply mitigations in accordance with N-able's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV due date of 11 September 2026 has passed, so unpatched servers are overdue.
- Upgrade N-central to 2026.3.1.14 or later. All versions before 2026.3.1.14, including the 2026.3 line, are affected — see the N-able security advisory for CVE-2026-86218 for the upgrade path and confirm the running version after the upgrade completes.
- Restrict access to the N-central web interface immediately. Until the upgrade is applied, limit the administrative interface to a management VPN or IP allowlist, and where agent check-in must remain reachable, front it with a WAF and restrict every other path — the vulnerability needs no credentials, so network reachability is the only real precondition.
- Assume compromise and hunt across both the server and managed endpoints. Review N-central for unexpected administrative users, scheduled tasks, automation policies and scripts, inspect web server logs for anomalous unauthenticated requests preceding the patch, and check managed endpoints for software or scripts pushed through N-central that no technician initiated. Rotate server credentials, API tokens, agent registration secrets and any customer credentials stored in the platform.
- Harden long term by never writing externally supplied input into files or records that are later interpreted as code, applying strict output encoding for the target format where such writes are unavoidable, keeping RMM platforms off the open internet wherever the architecture allows, and enforcing multi-factor authentication on all N-central accounts so that credential theft alone does not extend an intrusion.
Technical Details
CVE-2026-86218 is a static code injection flaw (CWE-96) in N-able N-central: input from an unauthenticated caller is persisted into a location that the platform later parses and executes as code, without neutralising the directives that the interpreter will act on. Unlike a direct code-injection sink where the payload executes during the same request, a static code injection writes first and executes later, which means the attacker's directives can persist across restarts and behave like a backdoor embedded in the application's own content — this is precisely why the vendor describes the outcome as pre-authentication remote code execution. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H reflects a network-reachable, low-complexity attack requiring no privileges and no user interaction, with full impact on confidentiality, integrity and availability at unchanged scope; scope remains unchanged because the code runs as the N-central application itself, which nonetheless holds the authority to manage every connected agent.
Frequently Asked Questions
Is CVE-2026-86218 being actively exploited?
Yes. CISA added CVE-2026-86218 to its Known Exploited Vulnerabilities catalog with a remediation due date of 11 September 2026, confirming exploitation in the wild. Because the flaw requires no authentication and N-central servers are commonly reachable from the internet, any unpatched instance should be treated as potentially already compromised.
What products are affected by CVE-2026-86218?
N-able N-central is affected in all versions before 2026.3.1.14, including the 2026.3 release line. N-able's security advisory for CVE-2026-86218 documents the affected versions and the fixed build.
How do I fix CVE-2026-86218?
Upgrade N-able N-central to version 2026.3.1.14 or later as described in N-able's security advisory. Until the upgrade is complete, restrict access to the N-central interface to trusted networks, and afterwards hunt for unauthorised admin accounts, scripts and automation policies and rotate all server credentials, API tokens and agent registration secrets.
How severe is CVE-2026-86218?
CVE-2026-86218 is Critical with a CVSS 3.1 base score of 9.8. It is unauthenticated, network-exploitable with low complexity and no user interaction, and grants remote code execution on the platform that manages an MSP's entire customer estate; the EPSS score sits near the 53rd percentile, but confirmed KEV-listed exploitation and the fan-out risk to managed endpoints make it an emergency patch.
Need Help With Vulnerability Management?
Our security experts can help you prioritize and remediate vulnerabilities effectively.