Skip to content
eastbaycyber

N-able blocks legacy APIs in N-central security update

Breaking news 7 min read
EC
East Bay Cyber Editorial Team Updated Developing story
Built from the vendor or authority notice plus independent reporting; unconfirmed claims are labeled as reported. Human-reviewed after publishing.

TL;DR - Since the last update, Rapid7 reported that exploitation involving N-central and CVE-2026-90436 is active, and N-able released the fixed version, N-central 2026.4 HF3, build 2026.4.1.39. - N-able permanently blocked legacy APIs and fixed CVE-2026-129271 through CVE-2026-129287. - N-able says on-premises customers should upgrade N-central servers as soon as possible. Hosted N-central servers are upgraded by N-able. - All hosted and on-premises customers must upgrade Agents and Probes to version 2026.4.1 HF3 to be fully protected. - Rapid7 recommends prioritizing internet-accessible instances with the relevant APIs enabled and investigating exposed systems for compromise.

What happened#

N-able released N-central 2026.4 Hotfix 3 on November 16, 2026. The release notes identify build number 2026.4.1.39 and describe the hotfix as a critical security update. It includes changes to authentication and access control, Agent and Probe security, file and import handling, server hardening, and user management. N-able’s release notes

The hotfix removes the configuration option for legacy APIs, and N-able says legacy APIs are now permanently blocked. The release also adds additional checks when Agents connect, an Inactive Assets tab, controls for managing inactive Agents, and new Network setup options for handling inactive Agents.

N-able lists 17 vulnerabilities fixed in the release, from CVE-2026-129271 through CVE-2026-129287. The issues include local privilege escalation, authentication bypass, missing authentication or authorization, command execution, user enumeration, XML external entity injection, server-side request forgery, remote code execution, audit log tampering, path traversal, and an origin validation error.

N-able also says devices now require either the SMBIOS ID or the machine ID to communicate with N-central. If both are missing, N-central rejects the connection.

Rapid7 reports that CVE-2026-90436, an unsafe reflection vulnerability in Apache Axis 1.x that can allow unauthenticated remote code execution, was actively exploited against N-central. Rapid7 says affected products required a non-default configuration and that N-central exploitation correlated with deployments where legacy APIs were enabled. Rapid7’s report was last updated on November 19, 2026. Rapid7’s report

SecurityWeek reports that attackers used the 4EverAble2Shell proof of concept after its public disclosure to deploy cryptocurrency miners. That claim has not been stated in N-able’s release notes.

Are you affected#

Organizations using hosted or on-premises N-central deployments should review the update. N-able says hosted N-central servers are upgraded by N-able, while customers running on-premises deployments should upgrade their servers as soon as possible.

All customers, hosted and on-premises, must upgrade all Agents and Probes to the latest version, 2026.4.1 HF3, to be fully protected. N-able says Agents and Probes that are not upgraded are susceptible to impersonation.

After Agents reconnect following an upgrade, N-able recommends reviewing the Inactive Assets tab. The tab is located under Configuration > Asset Discovery > Discovered Assets. It lists Agents that N-central has made inactive next to the active Agent for the same device. N-able says the tab may initially be empty and fills as Agents reconnect after an upgrade.

Inactive Agents can result from cloning, re-imaging or rebuilding a machine, a second Agent installation, restoring the N-central server from a backup, an administrator making another Agent active, another Agent reconnecting first after a server upgrade, or an Agent returning after its token is no longer valid.

Administrators can use Set Active, Delete, and Export from the Inactive Assets tab. N-able says these actions are logged for audit. The Network setup page includes additional options for managing inactive Agents, including whether they are rejected or required to upgrade.

Rapid7 recommends prioritizing internet-accessible instances with relevant APIs enabled and checking internal deployments as well. Its report lists these N-central indicators of compromise: 157.20.241[.]16, 139.99.69[.]109, and 79.76.51[.]56. Rapid7 cautions that the absence of these addresses does not confirm that an environment was unaffected.

What is confirmed and what is reported#

Claim Source Status
N-central 2026.4 HF3 was posted on November 16, 2026, with build number 2026.4.1.39. N-able Confirmed
Legacy APIs are permanently blocked in N-central 2026.4 HF3. N-able Confirmed
The release fixes CVE-2026-129271 through CVE-2026-129287. N-able Confirmed
N-able says hosted N-central servers are upgraded by N-able. N-able Confirmed
Customers must upgrade Agents and Probes to 2026.4.1 HF3 to be fully protected. N-able Confirmed
Devices missing both the SMBIOS ID and machine ID are rejected when connecting to N-central. N-able Confirmed
Rapid7 reports active exploitation involving N-central and CVE-2026-90436. Rapid7 Reported
Rapid7 recommends emergency remediation for exposed systems and lists N-central indicators of compromise. Rapid7 Reported
Threat actors used the 4EverAble2Shell proof of concept in attacks to deploy cryptocurrency miners. SecurityWeek Reported
The N-central vulnerabilities were disclosed publicly as zero-days. SecurityWeek Reported

What defenders should do now#

  1. On on-premises deployments, upgrade N-central servers to N-central 2026.4 HF3, build 2026.4.1.39, as soon as possible, following N-able’s release guidance.

  2. Confirm that all Agents and Probes are upgraded to version 2026.4.1 HF3. N-able says unupgraded Agents and Probes are susceptible to impersonation.

  3. For hosted deployments, determine whether the hosted server upgrade has been completed through the responsible N-able service process, and still upgrade all Agents and Probes.

  4. After Agents reconnect, review Configuration > Asset Discovery > Discovered Assets, then select the Inactive Assets tab. N-able says the tab fills as Agents reconnect and may be empty at first.

  5. Investigate inactive Agents and use Set Active, Delete, or Export as appropriate. N-able says these actions are logged for audit.

  6. Review Administration > Mail and Network Settings > Network Setup, including the Appliance token behaviour section, and apply the available inactive-Agent controls as appropriate. N-able says changes take effect immediately and do not require a server restart.

  7. Prioritize internet-accessible N-central instances and check internal deployments, particularly where relevant APIs were enabled, following Rapid7’s guidance.

  8. Investigate exposed systems for evidence of compromise. Review logs and telemetry for the N-central indicators listed by Rapid7: 157.20.241[.]16, 139.99.69[.]109, and 79.76.51[.]56. Rapid7 cautions that the absence of these addresses does not confirm an environment was unaffected.

  9. Treat any evidence of exploitation, unexpected command execution, or unauthorized changes as an incident requiring investigation and response.

This advisory is informational and is updated as vendors publish details. Confirm versions and actions against N-able’s guidance for your environment.

This advisory is informational and is updated as vendors publish details. Confirm versions and actions against the vendor’s own guidance for your environment.

Sources

Last verified: 2026-11-20

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.