N-able N-central Pre-Auth RCE (CVE-2026-86218, CVSS 10.0) Exploited in the Wild; CISA KEV Deadline September 11
CISA added CVE-2026-86218, a maximum-severity (CVSS 10.0) pre-authentication remote code execution flaw in N-able N-central that the vendor confirms is exploited in the wild, to its KEV catalog; on-premises admins must update to 2026.3.1.14 (2026.3 Hotfix 4)…
CISA added CVE-2026-86218 to its Known Exploited Vulnerabilities catalog on September 8, 2026, following N-able's confirmation that the flaw is being exploited in the wild. The vulnerability is a static code injection flaw (CWE-96) enabling unauthenticated remote code execution on exposed N-central servers, carrying a CVSS score of 10.0. It affects all on-premises builds prior to 2026.3.1.14 across the 2025.4 through 2026.3 release lines; the fix ships as N-central 2026.3 Hotfix 4 (version 2026.3.1.14), reported as released September 5 by The Hacker News and September 5–6 by Cyber Security News. Hosted environments were patched server-side by the vendor. Under BOD 26-04, US federal civilian agencies must mitigate by September 11, 2026, and the Canadian Centre for Cyber Security issued advisory AV26-885 urging immediate application of the hotfix. Huntress is investigating the compromise of a customer N-central instance on September 4 — two days before the hotfix shipped — and, per The Hacker News, the affected server was fully patched and Huntress cannot yet confirm which flaw was used. Separately, Rapid7-disclosed CVE-2026-86206 and CVE-2026-86207 can be chained by an unauthenticated attacker to create a rogue System Administrator account; Cyber Security News notes this is N-able's fourth emergency hotfix in five weeks.
- CVE-2026-86218: CVSS 10.0, CWE-96 static code injection enabling pre-authentication/unauthenticated RCE in N-able N-central
- N-able confirmed the flaw is being exploited in the wild
- CISA added CVE-2026-86218 to the KEV catalog on September 8, 2026; BOD 26-04 requires federal civilian agencies to mitigate by September 11, 2026
- Affected: all on-premises N-central builds prior to 2026.3.1.14 across the 2025.4–2026.3 release lines; fix is 2026.3 Hotfix 4 (reported released September 5 or September 5–6, 2026, depending on source)
- Hosted/cloud N-central environments were patched server-side
- Huntress is investigating a customer N-central compromise on September 4, 2026; The Hacker News reports the server was fully patched and the flaw used is not yet confirmed
- Related Rapid7-disclosed flaws CVE-2026-86206 and CVE-2026-86207 can be chained by an unauthenticated attacker to create a rogue System Administrator account
- Canadian Centre for Cyber Security advisory AV26-885 urges immediate application of the hotfix
Coverage timelineoldest first · each row is one article
- · 7d agoN-able security advisory (AV26-885)
Canadian Centre for Cyber Security· 66
N-able says CVE-2026-86218 in N-central is exploited in the wild; MSPs must apply hotfix 2026.3.1.14 (2026.3 HF4).
Vulnerabilities in this storyAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-86206 | Access Control Filter Bypass in N-able N-central Exposes Internal APIs N-able N-central contains a flaw in the access-control filter that protects its internal API (CWE-791, incomplete filtering), allowing requests to bypass the filter and reach internal APIs without authorization. The issue is exploitable over the network with no privileges and no user interaction, per the CVSS 4.0 vector (AV:N/PR:N/UI:N). An attacker gains unauthorized, low-impact access to internal APIs (VC:L); the vector indicates no integrity or availability impact and no evidence of code execution from this flaw. Any organization running an affected N-central release — a remote monitoring and management (RMM) platform operated by managed service providers — is affected, and the fix is available in N-central 2026.3 HF3 and 2026.4. The flaw is not on the CISA KEV list and has no known public PoC or confirmed in-the-wild exploitation, though it was disclosed in the same patching cycle as actively exploited N-central unauthenticated RCE flaws. Do: Upgrade N-central to 2026.3 HF3 or 2026.4 as soon as practical. While patching, limit direct internet exposure of the N-central API and check logs for unauthenticated requests to internal API endpoints. Note this release cycle included several recent N-central hotfixes, including an actively exploited unauthenticated RCE, so ensure all outstanding patches are applied. | 6.9 | <1% |
| large≈ tens of thousands of N-central server deployments (MSP RMM installs), with only the internet-exposed subset directly reachable | ||
| CVE-2026-86207 | Authentication bypass in N-able N-central internal APIs before 2026.3 HF 3 CVE-2026-86207 is an authentication bypass (CWE-305) in N-able's N-central remote monitoring and management (RMM) platform that allows unauthorized access to APIs that are supposed to be internal-only. It is triggered over the network by sending requests to these internal API endpoints under specific conditions (the CVSS vector indicates some attack prerequisites and a low-privilege foothold are required). An attacker who exploits it gains highly privileged access to the N-central server's data and functions, with high impact on confidentiality, integrity and availability of the server itself. Organizations running any N-central release before version 2026.3 Hotfix 3 are affected — primarily managed service providers hosting N-central for their own operations. There is no public proof of concept, the flaw is not in CISA's KEV catalog, and EPSS puts 30-day exploitation risk at just 0.7%; note that the recent news headlines about actively exploited 'unauthenticated RCE' flaws in N-central describe separate vulnerabilities in the same product, which is why multiple hotfixes have shipped in quick succession. Do: Upgrade all N-central servers to version 2026.3 HF 3 or later, or apply the vendor's hotfix to your current release. Restrict network access to the N-central web/API interface to trusted networks and review logs for unexpected access to internal API endpoints. Given the recent string of N-central fixes — including the separately exploited pre-auth RCE — verify that every recent hotfix has been applied to each N-central instance you operate. | 7.7 | <1% |
| moderate≈ several thousand to low tens of thousands of N-central server deployments (typically one internet-exposed server per MSP) | ||
| CVE-2026-86218 | Pre-Auth Static Code Injection RCE in N-able N-central (Exploited in the Wild) CVE-2026-86218 is a static code injection flaw (CWE-96) in N-able's N-central on-premises remote monitoring and management (RMM) platform, carrying a maximum CVSS 4.0 score of 10.0. An unauthenticated, remote attacker triggers it by sending crafted network input to the N-central server that is improperly neutralized and persisted into application-managed code, which the server then executes — no privileges (PR:N) or user interaction (UI:N) are required. Successful exploitation yields full server compromise with high impact on confidentiality, integrity, and availability, and because N-central acts as the management hub for downstream customer endpoints, compromise can expose the entire managed estate. Any organization running an affected N-central release (before 2026.3.1.14) — primarily MSPs and corporate IT departments using N-able RMM — is affected. The flaw is confirmed exploited in the wild: N-able patched it as a zero-day, CISA added it to the KEV catalog on 2026-09-08, and it is the fourth N-central hotfix in five weeks, though no public PoC is known and ransomware use is unknown. Do: Upgrade N-central to 2026.3.1.14 or later (or apply N-able's hotfix) immediately, as the flaw is in CISA's KEV catalog and BOD 26-04 timelines apply to federal stakeholders. Until patched, remove direct internet exposure of the N-central server (restrict to VPN/management networks via firewall allowlists) since no authentication is needed for exploitation. Because in-the-wild exploitation is confirmed, review internet-facing N-central servers for indicators of compromise such as unexpected processes, unusual child processes of the web service, and new or suspicious accounts. | 10.0 | <1% | KEV PoC ×2 |
| large≈ tens of thousands of deployed/internet-exposed N-central servers (order of magnitude ~10k+), each managing many downstream customer endpoints |