N-able hotfix shuts off N-central legacy API used in attacks
N-central 2026.4 Hotfix 3 fixes 17 new CVEs and permanently blocks the legacy APIs that attackers used via a critical Apache Axis flaw, which Rapid7 now sees hitting Confluence.
- What happened
- N-able released N-central 2026.4 Hotfix 3 on 16 November, fixing 17 vulnerabilities and removing the option to enable legacy APIs.
- What’s new
- Legacy APIs are now permanently blocked, which SecurityWeek says stops the 4EverAble2Shell exploit chain attackers used to plant cryptocurrency miners.
- Why it matters
- On-premises servers and every Agent and Probe need upgrading, and the same Axis bug is being exploited against Confluence Data Center.
N-able released N-central 2026.4 Hotfix 3 on 16 November, which it describes as a critical update. The release fixes 17 newly assigned vulnerabilities and removes the setting that let administrators turn on the product's legacy APIs. According to SecurityWeek, the flaws are tracked as CVE-2026-129271 through CVE-2026-129287. They include privilege escalation, command execution, missing authentication and authorisation, audit log tampering, user enumeration, XXE injection, SSRF and remote code execution bugs. Rapid7 gives the build number as 2026.4.1.39.
Why the legacy API change matters
Attackers have been reaching N-central through the legacy API. A researcher published an exploit chain called 4EverAble2Shell on GitHub on 12 November. SecurityWeek says the chain combines CVE-2026-90436, a critical remote code execution bug in Apache Axis, with an N-central flaw on deployments that have legacy APIs switched on, letting an attacker run a shell script as root. Within hours of the release, attackers were using the code to install cryptocurrency miners, SecurityWeek reports. N-able's release notes say legacy APIs are now permanently blocked, and SecurityWeek says this shuts down the chain.
Rapid7 says N-able reported in-the-wild exploitation of N-central on 13 November, involving a vulnerability that strongly correlates with the Axis bug. Before Hotfix 3 arrived, Rapid7 advised on-premises administrators to check that Legacy API was disabled, even on Hotfix 2. N-able states the feature is off by default.
N-able says it has already patched hosted environments and urges on-premises customers to upgrade quickly. Customers on both hosted and on-premises deployments must also upgrade their Agents and Probes. N-able warns that any left on older versions can be impersonated. Hotfix 3 also hardens authentication, Agent and Probe communication, and file and XML import handling. It also requires devices to be identified before they can connect to N-central. Rapid7 recommends treating the upgrade as an emergency, outside normal patch cycles.
The Axis bug reaches Confluence
CVE-2026-90436 affects more than N-central. According to Rapid7, Apache disclosed the flaw on 6 November as an unsafe reflection weakness in Axis 1.x that allows unauthenticated code execution. Because the 1.x branch is end of life, Apache will not ship a fixed release. Apache instead recommends moving to another SOAP engine or using a patched build, Rapid7 says. Rapid7's managed detection team saw the flaw being exploited against Confluence Data Center at a customer on 13 November.
Atlassian's advisory says Confluence is exposed only when its Remote API (XML-RPC & SOAP) setting is enabled. That setting has been disabled by default on new installations since version 3.0 and was removed entirely in 10.0. Confluence versions 1.x to 9.x are affected, 9.2.28 is the fixed release, and Atlassian Cloud is not affected. Administrators who cannot patch yet can clear the setting without a restart. Atlassian warns that scripts, automations and third-party add-ons relying on the API may break if they do. Atlassian also says it cannot confirm whether customer instances were compromised and advises security teams to inspect affected systems.