N-able ships N-central 2026.4 HF3, patching 17 CVEs
N-able's N-central 2026.4 Hotfix 3 (build 2026.4.1.39) patches 17 CVEs and permanently blocks the legacy API that a live cryptomining chain abused. On-prem admins should upgrade now.
N-able released N-central 2026.4 Hotfix 3 on November 16, a critical update that fixes 17 CVEs and permanently closes the legacy API surface that recent exploitation leaned on. The primary source is N-able's own 2026.4 HF3 release notes; the exploitation context was reported by The Hacker News. If you self-host N-central, upgrade on-premise servers to build 2026.4.1.39 as soon as possible.
What's fixed
N-able assigned the fixes a contiguous block, CVE-2026-129271 through CVE-2026-129287 — 17 identifiers in all. The release notes list the IDs but publish no per-CVE CVSS scores, descriptions, or affected-component breakdown, so the relative severity of individual flaws is not public at the time of writing.
The most concrete hardening in HF3 is structural: N-able writes that it has "removed the configuration option for legacy APIs, and legacy APIs are now permanently blocked." That matters because the active-exploitation chain against N-central reached code execution through N-central's legacy API mode.
Why it's urgent
HF3 lands on top of a run of real attacks. We covered the exploitation: researcher Sean Bales published the 4EverAble2Shell and Agent2Shell chains on November 12, and Huntback tied a single attacker host to 21 compromised N-central servers running the XMRig Monero miner — with 19 of the 21 already on Hotfix 2. The lesson from that incident was that patching HF2 alone did not stop the chain.
HF3's permanent removal of the legacy API is the change that closes that specific path rather than merely patching around it. N-able does not state in the release notes whether any of the 17 new CVEs correspond to the Bales chains, and it does not mention cryptomining — so treat the version bump as the fix and the earlier compromises as unrelated to these particular CVE assignments unless N-able says otherwise.
Action checklist
- Upgrade on-premise N-central to 2026.4.1.39 using the upgrade instructions on the N-able support portal. Supported direct upgrade paths include 2026.4 Hotfix 2 (build 2026.4.1.26); older builds must first move to a listed intermediate build.
- Hosted (N-able-managed) servers require no server-side action — N-able upgrades those — but you still need to update endpoints.
- Upgrade all Agents and Probes to 2026.4.1 HF3. N-able states you are "fully protected" only once agents and probes are also on HF3.
- Treat any server that ran a vulnerable build as suspect. Given the prior XMRig activity, hunt for unexpected miners, systemd/cron persistence, and outbound pool traffic before assuming a clean patch closed the door.
Context
This is the third N-central security event in short order — the cloud pull during the Able2Shell disclosure, the 4EverAble2Shell XMRig wave, and now a 17-CVE hotfix that finally retires the legacy API. RMM platforms are high-value because one compromised server reaches every managed endpoint below it, which is exactly why miner operators and ransomware affiliates keep probing them. The permanent removal of a legacy interface is the right move; the open question N-able has not answered is why a contiguous block of 17 CVEs ships without a single public severity score to help operators prioritize.