N-able Rushes Patch for Max-Severity RCE Flaw Under Attack

Nearly 1,500 N-central servers are exposed online — most in the United States and Europe — while N-able urges immediate patching after releasing an emergency hotfix for a maximum-severity remote code execution flaw.

N-able issues N-central 2026.3 Hotfix 4

N-able released an emergency hotfix it calls N-central 2026.3 Hotfix 4 to address a maximum-severity remote code execution (RCE) vulnerability affecting its N-central remote monitoring and management (RMM) platform. The company has urged customers to patch "as soon as possible" and said, "Customers running on-premises N-central deployments should upgrade to N-central 2026.3 HF4 immediately to protect their environment." N-able also stated, "At this time, we have no confirmations that this vulnerability has been exploited in production environments, but unpatched systems remain at risk."

The flaw: CVE-2026-86218 and related CVEs

The RCE is tracked as CVE-2026-86218. According to the advisory, the vulnerability "allows threat actors without privileges to execute malicious code on unpatched N-central instances exposed online in low-complexity attacks." Over the same weekend, N-able also patched two high-severity vulnerabilities tracked as CVE-2026-86206 and CVE-2026-86207; those flaws can allow attackers to bypass authentication and gain full access to vulnerable N-central platforms.

Evidence of exploitation and Huntress's analysis

Cybersecurity company Huntress flagged CVE-2026-86218 as a potential zero-day alongside CVE-2026-86206 and CVE-2026-86207. In a 9/5/26 update, Huntress said it "could not rule out whether the two previous vulnerabilities released (CVE-2026-86206 and CVE-2026-86207) were the ones that were exploited in the instance seen in the patched production environment of one of our customers." Huntress added that, because "logs on the compromised N-central server had already rotated, we are also unable to say whether this new CVE was the vulnerability exploited in that case."

Huntress warned that "On-premises N-central users must apply HF4 immediately, as systems running HF3 remain vulnerable to this newly disclosed flaw."

Internet exposure: Shadowserver Foundation's tally

Internet security nonprofit Shadowserver Foundation now tracks nearly 1,500 N-central servers exposed online, with most located in the United States and Europe. The scale of exposed instances mirrors past findings: one year ago, after N-able released security updates for two N-central vulnerabilities (CVE-2025-8875 and CVE-2025-8876) that attackers were exploiting in the wild, Shadowserver found that 880 N-central servers were still vulnerable even after CISA ordered federal agencies to patch their systems within a week and urged all security teams to prioritize securing their systems against ongoing attacks.

What this means for managed service providers, federal agencies, and security teams

• Managed service providers and on-premises N-central administrators: The concrete step N-able and Huntress have urged is immediate upgrade to N-central 2026.3 Hotfix 4. Because the RCE allows unauthenticated code execution on exposed instances, unpatched servers "remain at risk."
• Federal agencies: Past precedent shows that even after a directed patching order from CISA, large numbers of N-central instances remained vulnerable. The earlier episode — where Shadowserver found 880 still exposed after a CISA patch directive — is a cautionary data point for federal patching efforts now.
• Security teams and incident responders: Huntress's inability to determine which CVE enabled the observed compromise — due to rotated logs — underscores a forensic constraint. In addition, the Blue Report 2026 reminder that "Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply" — based on defenses measured across 338 million simulations — is directly relevant to defenders evaluating their post-access detection and response controls.

The immediate technical answer from both the vendor and external researchers is unambiguous: patch. N-able has published N-central 2026.3 HF4 and warned on-premises customers to upgrade, and Huntress has flagged systems still on HF3 as vulnerable. Yet the broader factual picture remains unsettled: Huntress documented a compromise in a patched production environment but cannot say which of the recent CVEs was used because relevant logs had rotated. With Shadowserver counting nearly 1,500 exposed instances, that combination — active exposure plus uncertainty about the exploited vector — leaves a narrow, practical path forward for operators: prioritize the hotfix, inventory internet-exposed N-central consoles, and preserve forensic data if a compromise is suspected.

Original source