In this article
  1. What happened
  2. Who’s affected
  3. What to do now
  4. Updates

Developing story, updated as details confirm.

What happened

New public exploits for N-able N-central, nicknamed 4EverAble2Shell, were released on November 12. N-able’s incident notice tells on-premises customers to make sure the Legacy API is disabled and says it is “developing additional remediation.” On November 13, it published indicators of compromise relevant only to Legacy API users.

Security firm huntback reports miners on 21 N-central servers, 19 of them on Hotfix 2, according to The Hacker News and BleepingComputer. N-able has not confirmed that count. Its remediation update lists no CVE for the November 12 issues, which it calls Legacy API abuse and Agent Impersonation. Hotfix 2 fixed seven CVEs from a November 9 disclosure: CVE-2026-125878 through CVE-2026-125883 and CVE-2026-91000. None is in CISA’s Known Exploited Vulnerabilities catalog.

Who’s affected

On-premises N-central servers with the non-default Legacy API turned on. The researcher says he tested against Hotfix 2 (2026.4.1.26). N-able says hosted customers need no server-side action. Small businesses may be exposed if their MSP’s on-premises N-central server is compromised.

What to do now

  1. Disable the Legacy API, as N-able advises. It is off by default.
  2. Check for compromise: huntback, quoted by The Hacker News, says to treat a hit as a full compromise, not a cleanup job.
  3. Keep Hotfix 2 and upgrade Agents and Probes, Agents first. N-able says Hotfix 3, in development, will permanently remove Legacy API access.

See our emergency patch checklist, ScreenConnect MSP attacks and news.

Updates

  • Nov 14, 2026, 8:58 a.m. Manila (UTC+8): Added N-able’s remediation update (dated November 13): the seven CVEs fixed in Hotfix 2, no CVE for the November 12 issues, and Hotfix 3 plans. Updated the incident’s IOC wording to its current text, including its November 13, 13:40 UTC update.

  • Nov 13, 2026, 2:36 p.m. Manila (UTC+8): Initial report, from N-able’s incident 202613 notice and its November 13 update, the Hotfix 2 release notes and N-able’s November 11 blog, with exploitation reports attributed to The Hacker News and BleepingComputer.

Sources & method

Last checked: Nov 14, 2026, 8:58 a.m. Manila (UTC+8). Method: We read N-able’s incident 202613 record through its official status API, the Hotfix 2 release notes and N-able’s November 11 blog at about 2:20 p.m. Manila (UTC+8) on November 13, re-checked incident 202613 and the release notes at 2:36 p.m., read N-able’s remediation update and re-checked CISA’s catalog at about 8:41 a.m. Manila on November 14, and re-read incident 202613 at 8:58 a.m. Manila. The 21-server and 19-on-Hotfix-2 figures are huntback’s, as reported by The Hacker News and BleepingComputer; N-able has not confirmed them. N-able’s notice still says “we have seen no signs of compromise,” while its later updates report IOCs; we quote the notice and paraphrase the updates. N-able’s remediation update gives CVEs only for the Hotfix 2 fixes, none for the November 12 issues, and no CVSS scores; it shows a date but no publication time. We do not reproduce exploit code. Thumbnail is a reuse-licensed photograph, cropped and resized, credited with its license under the picture. No affiliate links. How we work.

Spotted an error? See our corrections policy and tell us.