N-central: Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') (CVE-2026-86218)
Published In CISA KEV since
What is affected, what to do
A critical code injection vulnerability (CWE-96) in N-able N-Central allows unauthenticated remote attackers to execute arbitrary server-side code without any user interaction. Successful exploitation grants full control over the affected system, compromising confidentiality, integrity, and availability. The vulnerability is actively exploited in the wild and has been added to the CISA Known Exploited Vulnerabilities catalog, underscoring the immediacy of the threat. Organizations running N-able N-Central must apply the available patch without delay and investigate their environments for signs of compromise.
The vulnerability is being actively exploited; treat it as a priority. Update N-able N-central to version 2026.3.1.14. Immediate actions, mitigation and detection rules are in the runbook below.
- Affected
- N-able N-central
lt *..2026.3.1.14
- N-able N-central
- Fixed in
- N-able N-central
2026.3.1.14
- N-able N-central
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
10.0
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v4
9.8
CVSS v3
Severity Critical on the scale from 0 to 10.
13.4 %
EPSS score
Elevated — model estimates 10-50% exploitation likelihood.
Source: FIRST EPSS, percentile 96.4
Show all metrics
- Severity
- Critical
Priority score
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 215.01
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploited (KEV)Source: VulnCheck KEV (opens in a new tab)
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 10.0
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.8
CVSS v4
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 10.0
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 13.4 %
- Elevated — model estimates 10-50% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 96.4
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossaryCWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-96
Response and mitigation
Why act now?
Prioritisation rationale
The flaw is reachable over the network without authentication or user interaction and yields full code execution on an RMM platform. Exploitation likelihood is very high. RMM servers are prime targets because one compromised instance hands the attacker legitimate remote control over every managed endpoint. For MSPs, that extends to every downstream customer, making this a supply-chain-style compromise. CISA currently does not flag known ransomware use, but the "own the RMM, then mass-deploy" pattern is a hallmark of extortion operations. Treat any internet-reachable N-central server as top priority with a patch window measured in hours. NIS2-scoped organisations and MSPs should also assess their incident-reporting obligations if any indicators of compromise surface.
Runbook step 1
Immediate response (0-24 h)
- Inventory: Identify every self-hosted N-central server (on-prem appliance or VM) and check the installed version in the admin console. Every version before 2026.3.1.14 is vulnerable. For hosted N-central, get written confirmation of the patch status from N-able or your MSP.
- Patch: Upgrade to N-central 2026.3.1.14 or later. Until the upgrade is complete, treat any internet-facing server as potentially compromised.
- Cut exposure now: If you cannot patch within hours, firewall the web/management UI so only known admin networks and the VPN can reach it. Restrict agent communication to known customer or site IP ranges where operationally feasible.
- Check for compromise before patching: Preserve a snapshot or forensic image of the appliance, plus web, application and system logs. Patching does not remove webshells or backdoors that are already in place.
- Rotate credentials (on suspicion or confirmed exposure): Renew N-central admin accounts, API tokens and integration keys (PSA, backup, SSO). Also rotate any domain or device credentials stored in the platform for managed endpoints.
- Freeze automation: Review new or recently modified Automation Policies, scripts and scheduled tasks. Disable anything unrecognised before it can push to managed endpoints.
Runbook step 2
Mitigation layers
- Network segmentation: Move the N-central server into a dedicated management zone. Allow egress only to required destinations (vendor update servers, mail relay, PSA). Block and log all other egress, especially outbound HTTP/HTTPS to arbitrary hosts.
- Pre-application access control: Expose the admin UI only through a VPN, ZTNA or a reverse proxy that enforces authentication (MFA/SSO) in front of it. This stops pre-auth exploitation at the network layer.
- WAF/IPS: Deploy vendor IPS/WAF signatures for CVE-2026-86218 as soon as they ship. In the interim, block unauthenticated requests to the N-central web UI that carry oversized or code-like parameters (Java/script expressions,
Runtime,exec,ProcessBuilder, Base64 blobs). - Appliance hardening: Limit local shell and SSH access to a bastion network. Put file-integrity monitoring (AIDE/auditd) on the web and application directories, and switch off unused services.
- IAM/least privilege: Reduce credentials stored in N-central to the minimum rights needed, and never use Domain Admin. Keep separate accounts per customer or site to contain blast radius.
- Endpoint side: Configure EDR to log processes launched by the RMM agent and block suspicious chains (e.g. agent → PowerShell download cradle).
Runbook step 3
Detection rules
- Server process ancestry (auditd/EDR): Watch for the N-central Java application-server process spawning shells or tooling such as
sh,bash,curl,wget,python,perlornc. Sigma shape:ParentImage|endswith: '/java' AND Image|endswith: ['/sh','/bash','/curl','/wget','/python3','/nc']. auditd:-a always,exit -F arch=b64 -S execve -F ppid=<java-pid> -k ncentral_exec. - Web/application logs: Look for unauthenticated POST requests with unusually long or code-bearing parameters, bursts of HTTP 500 errors from a single source, and new or unknown JSP or script files in web directories. Alert via FIM on
*.jspand*.classfiles written outside upgrade windows. - Network telemetry (Zeek/Suricata): Flag outbound connections from the N-central server to unknown IPs or domains, especially right after inbound internet requests. Zeek approach:
conn.logwhereid.orig_h == <ncentral_ip>and the destination is not on the allowlist. - RMM abuse (EDR, Sysmon EID 1): Watch for the same new script or binary running on many endpoints within minutes via the N-central agent. KQL:
DeviceProcessEvents | where InitiatingProcessFileName has "agent" and FileName in~ ("powershell.exe","cmd.exe","rundll32.exe") | summarize dcount(DeviceName) by ProcessCommandLine, bin(Timestamp,15m) | where dcount_DeviceName > 10. - N-central audit trail: Track new admin users, role changes, new API keys, new Automation Policies, and remote sessions outside maintenance windows. Forward these events via syslog to the SIEM and correlate them against known admin accounts.
- Server process ancestry (auditd/EDR): Watch for the N-central Java application-server process spawning shells or tooling such as
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
N-central is vulnerable to a pre-auth remote code execution This issue affects N-central: before 2026.3.1.14.
Source: BSI WID Portal
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| N-able | N-central |
|
|
| n-able | n-central |
|
|
| N-able | N-Central |
|
|
Weakness classes (CWE)
CWE-96Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')
Base
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before inserting the input into an executable resource, such as a library, configuration file, or template.
Entry at MITRE CWE-96
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| Source | Reference | Maturity | Published |
|---|---|---|---|
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited (KEV) | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-86218 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-86218 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-86218-N-central-IOC-Toolkit (opens in a new tab)github.com | PoC (publicly reported)reported, not verified | |
| PoC-in-GitHub (nomi-sec) | CVE-2026-86218 (opens in a new tab)github.com | PoC (publicly reported)reported, not verified |
References & sources
- me.n-able.coms/security-advisory/aArVy0000002Ld3KAE/cve202686218-preauthenti…Vendor advisory
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2026-86218government-resource
- documentation.n-able.comN-central/Release_Notes/GA/Content/N-central_2026.3_HF3_Release…Release notes
- me.n-able.coms/security-advisory/aArVy0000002LUzKAM/cve202686207-authenticat…Vendor advisory
- me.n-able.coms/security-advisory/aArVy0000002LTNKA2/cve202686206-access-cont…Vendor advisory
Reanalysis & status changes
Chronological NVD audit events for this CVE — reanalyses, CVSS updates, CPE diffs.
CVE Modified134c704f-9b21-4f2e-91b3-4a467353bcc0
- SSVC:
before {"id":"CVE-2026-86218","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technic…after {"id":"CVE-2026-86218","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technic…
- SSVC:
Initial Analysisnvd@nist.gov
- CVSS V3.1: after AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CPE Configuration: after OR *cpe:2.3:a:n-able:n-central:*:*:*:*:*:*:*:* versions up to (excluding) 2026.3 *cpe:2.3:a:n-able:n-central:2026.3:-:*:*:*:*:*:* *cpe:2.3:a:n-able:n-central:2026.3:hotfix1:*:*:*:*:*:* *cpe:2.3:a:n-able:n-central:2026.3:hotfix2:*:*:*:*:*:* *cpe:2.3:a:n-able:n-central:2026.3:hotfix3:*:*:*:*:*:*
- Reference Type: after CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-86218 Types: US Government Resource
- Reference Type: after N-able: https://me.n-able.com/s/security-advisory/aArVy0000002Ld3KAE/cve202686218-preauthentication-remote-code-execution Types: Vendor Advisory
CVE Modified134c704f-9b21-4f2e-91b3-4a467353bcc0
- Reference: after https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-86218
- SSVC:
before {"id":"CVE-2026-86218","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technical…after {"id":"CVE-2026-86218","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technic…
CVE CISA KEV Update9119a7d8-5eab-497f-8521-727c672e3725
- Date Added: after 2026-09-08
- Due Date: after 2026-09-08
- Required Action: after 2026-09-08
- Vulnerability Name: after 2026-09-08
CVE Modified134c704f-9b21-4f2e-91b3-4a467353bcc0
- SSVC:
before {"id":"CVE-2026-86218","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technical…after {"id":"CVE-2026-86218","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technical…
- SSVC:
Linked CVEs
| Severity | CVE | Title | CVSS | Exploitation |
|---|---|---|---|---|
| Critical | CVE-2026-86218 | pre-authentication remote code execution | 9.8 | Actively exploited |
| High | CVE-2026-86207 | Authentication bypass leads to unauthorised access to N-central | — | — |
| Medium | CVE-2026-86206 | Access control filter bypass allows unauthorised access to APIs | — | — |