N-able vulnerabilities in 2026: N-central zero-days, KEV listings and CVE-2026-90436 (not a breach of N-able)
N-able sells N-central, remote monitoring and management software that IT teams and managed service providers use to run commands on every machine they manage. A flaw in an N-central server is therefore a path to all of those machines. This page tracks the N-central vulnerabilities of 2026 and keeps N-able's own statements apart from what researchers and CISA say.
Short answer
Was N-able hacked?
No breach of N-able's own systems is reported in the sources we read. What is reported are vulnerabilities in N-central. CISA added three N-central flaws to its Known Exploited Vulnerabilities catalog in 2026: two authentication bypasses (CVE-2026-18577 and CVE-2026-18556, added 3 and 4 August) and a pre-authentication code-injection flaw (CVE-2026-86218, added 8 September).
In November 2026 researchers published N-central zero-days without coordinated disclosure. N-able says the server issue disclosed on 12 November depends on the non-default Legacy API being enabled and exposed, and it has published indicators of compromise for customers who had not disabled it. N-central 2026.4 HF3 (2026.4.1.39, 16 November) permanently blocks the legacy APIs and fixes 17 more CVEs. Rapid7 and Previdian tie the November attacks to CVE-2026-90436 in Apache Axis; N-able's own notices do not name that CVE.
Timeline at a glance
3-4 Aug 2026CISA adds N-central authentication bypasses CVE-2026-18577 and CVE-2026-18556 to KEV. (CISA)Not a breach
8 Sep 2026CISA adds N-central pre-authentication code injection CVE-2026-86218 to KEV. (CISA)Not a breach
9-12 Nov 2026N-central zero-days published without coordinated disclosure; N-able takes hosted servers offline after the first, says the 12 Nov server issue needs the non-default Legacy API. (N-able)Not a breach
12-13 Nov 2026Previdian reports attempts starting with Apache Axis CVE-2026-90436; N-able publishes IOCs for customers with the Legacy API enabled. (The Hacker News; N-able)Reported
16 Nov 2026N-central 2026.4 HF3 (2026.4.1.39) permanently blocks legacy APIs and fixes CVE-2026-129271 to CVE-2026-129287. (N-able)Not a breach
Last updated 19 November 2026. Every entry is dated and linked to its source; claims by attackers are labelled as claims, never stated as fact.
N-able incident timeline, in detail
Confirmed = acknowledged by N-able, a regulator filing or a court. Reported = credible reporting N-able has not fully confirmed. Unverified claim = an attacker or leak-site claim.
Nov 2026Not a breachProduct vulnerabilities (server and agents)
November zero-days, the Legacy API and the Apache Axis link
What happened. N-able grouped the November disclosures into authenticated and product-admin data leakage (9 November), and Legacy API abuse and agent impersonation (12 November). It says the Legacy API is off by default and not a recommended configuration. 2026.4 HF2 addressed the internet-facing unauthenticated issues; HF3 (2026.4.1.39) removes the Legacy API option, hardens agent and probe authentication and fixes CVE-2026-129271 to CVE-2026-129287. N-able lists CVE-2026-125878 to CVE-2026-125883 and CVE-2026-91000 among the fixed issues too.
Impact. N-able says it identified indicators of compromise relevant only to customers who had not disabled the Legacy API, and that agents and probes not upgraded are susceptible to impersonation. Rapid7 says N-able reported in-the-wild exploitation of a vulnerability that "strongly correlates" with Apache Axis CVE-2026-90436, and The Hacker News reported Previdian's finding of an attack chain that began with that flaw, with no evidence of success at the time. Hosted customers: N-able upgrades the server; agents and probes are the customer's job.
Aug-Sep 2026Not a breachProduct vulnerabilities, known exploited
Three N-central flaws added to CISA KEV
What happened. CVE-2026-18556 (authentication bypass using an alternate path, added 4 August), CVE-2026-18577 (authentication bypass, which CISA describes as the result of an incomplete patch for CVE-2026-18556, added 3 August) and CVE-2026-86218 (static code injection allowing pre-authentication remote code execution, added 8 September).
Impact. CISA lists all three as known exploited, with ransomware use "Unknown". The KEV entries point to N-central 2026.3 hotfixes.
CVE-2026-90436: Rapid7, Previdian (via The Hacker News) and Field Effect link N-central to the Apache Axis flaw. N-able's notices we read on 19 November 2026 name other CVEs and do not mention Apache Axis.
Exploitation: The Hacker News (12 November) reported no evidence of successful exploitation at the time; N-able later said it had identified indicators of compromise for customers with the Legacy API enabled. Rapid7 describes N-able as having reported in-the-wild exploitation.
KEV order: CISA dates CVE-2026-18577 (3 August) a day before CVE-2026-18556 (4 August), although it describes the first as an incomplete patch for the second.
The pattern across the record
RMM servers are master keys
An N-central server can run commands on every managed machine, so its flaws are exploited fast and repeatedly. Treat it as tier-0.
Legacy options keep attack surface alive
The November server issue needed an API that was off by default. HF3 removed the option instead of leaving it to configuration.
What it means for N-able customers — and what to do
If you run N-central, on-premises or hosted, the question is your server build, your agents and probes, and whether the Legacy API was ever on, not whether N-able was breached.
1.Upgrade to 2026.4 HF3
Server to 2026.4.1.39 and every agent and probe to HF3. Hosted: N-able upgrades the server; you upgrade agents and probes.
No breach of N-able's own systems is reported. The 2026 issues are vulnerabilities in N-central, several of them exploited against customers' servers.
Which N-central build should I run?+
N-central 2026.4 HF3 (2026.4.1.39), released 16 November 2026, with all agents and probes upgraded to HF3.
Is N-central affected by Apache Axis CVE-2026-90436?+
Rapid7 says 2026.4 HF2 is affected when the Legacy API is enabled, and links N-able's exploitation report to the CVE. N-able's own notices do not name it. HF3 permanently blocks the legacy APIs.
More in the Breach Index
Same sourced, verification-tagged timeline, company by company — compare how peers have fared.
Independent analysis for security-leadership education; not affiliated with or endorsed by N-able. Facts are attributed to the dated sources above, and anything disputed or unconfirmed is labelled as such. See the full Breach Index.