Vendor History
IT management, remote access and backup
N-able security incident history
Updated . Data gathered daily from official public sources.
As of Oct 26, 2026, Vendor History found 5 actively exploited security flaws for N-able, dated Aug 13, 2025 to Sep 8, 2026. Sources checked: the California and Washington Attorney General breach lists, SEC EDGAR (Form 8-K, Item 1.05) and CISA's Known Exploited Vulnerabilities catalog.
Breach notices and SEC cyber filings
None found in the sources we check.
Got a breach letter from N-able? What to do when a vendor has a data breach.
Actively exploited security flaws
Flaws in N-able products that CISA lists as exploited by attackers. If you use an affected product, check that it's updated. What a listing means.
-
N-able N-central Static Code Injection Vulnerability (CVE-2026-86218). Added to CISA's list of security flaws known to be exploited by attackers.
-
N-able N-central Authentication Bypass Using an Alternate Path or Channel Vulnerability (CVE-2026-18556). Added to CISA's list of security flaws known to be exploited by attackers.
-
N-able N-central Authentication Bypass Using an Alternate Path or Channel Vulnerability (CVE-2026-18577). Added to CISA's list of security flaws known to be exploited by attackers.
-
N-able N-Central Insecure Deserialization Vulnerability (CVE-2025-8875). Added to CISA's list of security flaws known to be exploited by attackers.
-
N-able N-Central Command Injection Vulnerability (CVE-2025-8876). Added to CISA's list of security flaws known to be exploited by attackers.
We check: California and Washington Attorney General breach notices, SEC cyber incident filings (Form 8-K, Item 1.05) and CISA's catalog of actively exploited security flaws. An empty section means we found nothing in those sources. It does not mean nothing happened. How it works
To cite: Vendor History, "N-able security incident history," vendorhistory.com/vendor/n-able, data checked Oct 26, 2026. Free to reuse under CC BY 4.0 with credit to Vendor History.