CISA lists five exploited N-central flaws from 2025 and 2026. If you run your own server, apply N-able's November updates first, then check whether anyone got in earlier.
Jump to the stepsDo the vendor steps on this page first. Then use our Secure N-central playbook for step-by-step guidance to secure your self-hosted appliance. It adds to patching and investigation. If you find unauthorized activity, include the managed devices in your response before you rely on the server again.
CISA lists five exploited N-central flaws in its Known Exploited Vulnerabilities (KEV) catalog: two from 2025 and three from 2026. In the August 2026 incident, attackers got administrative access without logging in. September brought a flaw that allows code execution before login. In November, new exploit chains were disclosed and N-able released new fixes and guidance.
N-able says Adlumin detected exploitation on July 31, 2026. The attacker used Take Control to reach managed devices, then registered Cloudflare tunnel services on those devices. So you need to check your managed devices, not only the server.
For CVE-2026-86218, N-able's own statements differ. Its September HF4 notice said it had no confirmation of exploitation in production. Its security blog said a third researcher reported the flaw had been exploited in the wild. CISA added it to KEV on September 8.
| CVE | CISA vulnerability name | Added to KEV | CISA due date |
|---|---|---|---|
| CVE-2026-86218 | Static Code Injection | September 8, 2026 | September 11, 2026 |
| CVE-2026-18556 | Authentication Bypass Using an Alternate Path or Channel | August 4, 2026 | August 7, 2026 |
| CVE-2026-18577 | Authentication Bypass Using an Alternate Path or Channel | August 3, 2026 | August 6, 2026 |
| CVE-2025-8875 | Insecure Deserialization | August 13, 2025 | August 20, 2025 |
| CVE-2025-8876 | Command Injection | August 13, 2025 | August 20, 2025 |
Check your full build under Help > Version Information, then compare it with the table. Each older hotfix fixed specific flaws, so an August or September build is not the current baseline. The newest release we found is 2026.4 HF2, build 2026.4.1.26, from November 10. N-able says more fixes are still in progress.
| CVE or release | Affected versions | Historical fix or November action |
|---|---|---|
| CVE-2025-8875 and CVE-2025-8876 | Before 2025.3.1 in the CVE records | 2025.3.1; also backported in 2024.6 HF2, build 2024.6.2.5. Both require authentication. |
| CVE-2026-18556 | Through 2026.1 | 2026.3 HF1, build 2026.3.1.7, on August 2. N-able then found a related attack path and released HF2, build 2026.3.1.10, on August 6. HF2 superseded HF1. Upgrading past 2026.1 alone is not enough. |
| CVE-2026-18577 | Through 2026.3.1, as quoted by Huntress | Follow-on to an incomplete fix for CVE-2026-18556. N-able's HF1 advisory names it; HF2 superseded HF1. |
| CVE-2026-86218 | Before 2026.3.1.14 | 2026.3 HF4, build 2026.3.1.14, on September 6. HF4 superseded HF3. |
| November 2026 guidance | More authenticated vulnerabilities still being fixed | 2026.4 HF2, build 2026.4.1.26, on November 10, plus turning off Legacy API. HF3 is coming. |
CVE-2026-86218 allows remote code execution before login. N-able scores it 10.0 under CVSS 4.0. Some reports cite 9.8 under CVSS 3.1; we could not confirm that score in a primary source. N-able scores CVE-2025-8875 and CVE-2025-8876 at 9.4 and CVE-2026-18556 at 8.2, also under CVSS 4.0.
September also included CVE-2026-86206 and CVE-2026-86207. Huntress reproduced a chain that could create unauthorized administrators. N-able then released HF3, which HF4 later superseded.
Back up the server, then upgrade along N-able's supported path and check the new build. Turn off Legacy API if you ever turned it on. Upgrade Agents, then Probes. Review users and automation, and replace credentials and API tokens that may have been exposed. If you suspect compromise, preserve evidence before you change anything.
Administration > System Backup and Restore > Download Backups.System Settings > N-central Server > Version Management. On earlier versions, use the N-central Administration Console (NAC) at /admin and Setup > Version Management. Don't reboot the server during the upgrade. Afterward, check Help > Version Information again.Administration > User Management > Users, including API-only users and integration accounts. Turn on MFA for each user under User Details > User Information > Access > Use Multi-Factor Authentication.Partly. N-able upgrades hosted servers, and on-premises customers must upgrade their own. Both groups must upgrade their Agents and Probes, so a hosted server update does not finish your work. Confirm the server build with N-able, roll out the Agent and Probe updates, and review suspicious activity in the environment you manage.
It depends on your server's build and settings. Huntress first advised shutting servers down, then said HF2 servers with Legacy API turned off are not exposed to the chain it described. N-able said on November 13 that more fixes were still coming. Upgrade, turn off Legacy API and check for earlier access before you trust the server.
Huntress reported no observed November exploitation in its partner environments at its November 13 update. That covers what Huntress can see, not every N-central server.
Start with unexpected administrators and account changes, then review remote sessions and automation. Huntress publishes account and appliance-log hunting leads; N-able adds November indicators for customers who had not disabled Legacy API. CISA's KEV entries establish exploitation history, but they cannot tell you whether attackers accessed your particular server.
.invalid account-name changes. Match role changes to authorized requests.Administration Utilities > View Logs > Download as a System/Product Administrator. Huntress highlights envoy_proxy_HTTPS.log and syslog ncentraldms; investigate encoded internal-API paths such as %2F in context./jup.sh and /xvgz. N-able scopes these indicators to customers who had not disabled Legacy API.Use the Secure N-central playbook for step-by-step guidance after the vendor steps. It is a $79 one-time PDF for on-premises N-central servers, with free email support on the solution at [email protected] and updates through the same download link. There are no refunds, so read the product details before buying.
We built this method on our own ScreenConnect server; this edition applies the same method to N-central servers, but we have not tested it on N-central.
As of November 15, 2026, the newest release we found is 2026.4 HF2, build 2026.4.1.26, released November 10. N-able said on November 13 that more authenticated vulnerabilities were still being fixed and HF3 was coming. Check N-able's status page before you upgrade. September's 2026.3 HF4 fixed an earlier flaw and is not the current baseline.
N-able upgrades hosted N-central servers, while on-premises customers must upgrade their own servers. Both hosted and on-premises customers must upgrade Agents and Probes. The November HF2 release notes specify Agents before Probes for compatibility. Confirm the hosted server's build with N-able and track endpoint upgrades in your own environment.
Huntress's November 12 update says HF2 servers with Legacy API disabled are not exposed to the described 4EverAble2Shell chain. Its November 13 update cites N-able confirmation that Agent2Shell also requires Legacy API enabled. Follow N-able's disablement guidance and subsequent remediation updates. Investigate earlier access even after you apply these changes.
Five, as of November 13, 2026. CISA added CVE-2025-8875 and CVE-2025-8876 on August 13, 2025, CVE-2026-18577 on August 3, 2026, CVE-2026-18556 on August 4, 2026, and CVE-2026-86218 on September 8, 2026. The 2025 pair are deserialization and command injection flaws, and the August pair are authentication bypasses. CISA lists ransomware use as Unknown for all five.
N-central supports TOTP multi-factor authentication, and you should turn it on for every user. It is not enough on its own: in the August 2026 incident, attackers got administrative access without logging in. MFA does not replace the server fixes or the Legacy API guidance. Review account changes and managed devices even if your team already used MFA.
Review unexpected administrators, account changes and remote sessions. Huntress highlights suspicious .invalid account-name changes, envoy_proxy_HTTPS.log, syslog ncentraldms and encoded internal-API paths such as %2F. Compare scheduled task and script changes with authorized work, and inspect managed devices. Save logs early: Huntress could not confirm which CVE was exploited after appliance logs rotated.
Yes, for any that may have been exposed. Replace administrator passwords, API-only user credentials and integration tokens, then update each integration that uses them. Follow each integration's own steps for replacing its credentials. If you suspect compromise, preserve evidence first so the change does not destroy records you need.
Research cutoff: November 15, 2026.
Incident guidance for other remote support platforms.