N-central zero-days patch: Hotfix 3 blocks legacy APIs used by 4EverAble2Shell, Agents and Probes need upgrades

N-central Zero-Days Patch: Hotfix 3 Blocks 4EverAble2Shell

N-able shipped N-central 2026.4 Hotfix 3 on Monday, fixing 17 zero-days (CVE-2026-129271 through CVE-2026-129287). This N-central zero-days patch also shuts the legacy APIs that 4EverAble2Shell, a public root exploit chain, abused. Attackers used the chain to plant cryptominers within hours of its November 12 release. N-able says hosted servers are patched. On-premises servers, and all Agents and Probes, still need upgrading.

Key takeaways

  • N-central 2026.4 Hotfix 3 patches 17 zero-days, CVE-2026-129271 through CVE-2026-129287; the reporting lists no CVSS scores.
  • Hotfix 3 removes the legacy API option, which N-able says defeats the 4EverAble2Shell root exploit chain.
  • N-able says hosted N-central is patched. On-premises servers, and all Agents and Probes in both setups, still need upgrading, or Agents and Probes can be impersonated.
  • Attackers used the public chain within hours of its November 12 release to deploy cryptocurrency miners. Treat any miner on an N-central server as a root compromise.
  • CVE-2026-90436 also hits Confluence with Remote API enabled; Atlassian fixed it in Confluence 9.2.28.

What is in the N-central zero-days patch, Hotfix 3?

Hotfix 3 is a security release for N-central, N-able’s remote monitoring and management (RMM) platform. It closes 17 vulnerabilities that had been dropped online as zero-days, filed as one contiguous block, CVE-2026-129271 through CVE-2026-129287. SecurityWeek, which reported the release, says the update also fixes flaws already exploited in attacks.

The bug classes include:

  • privilege escalation and command execution, up to remote code execution
  • missing authentication or authorization checks
  • a predictable passcode and user enumeration
  • audit log tampering
  • XML external entity (XXE) injection and server-side request forgery (SSRF)
  • assorted validation errors

Two of those need a plain-English gloss. XXE means the XML parser follows references an attacker slipped into a document, which can leak local files or make the server fetch things on the attacker’s behalf. SSRF makes the server send requests for the attacker, often to admin interfaces or cloud metadata services that only the server itself can reach.

That explains why the hardening goes well beyond logins. Hotfix 3 builds on Hotfix 2 and tightens authentication, Agent and Probe communication, file and XML import handling, request and outbound connection handling, and user management.

Some gaps remain. N-able calls the update critical, but no CVSS scores appear in the reporting for the 17 CVEs. The coverage does not say which fixed flaws attackers exploited beyond the 4EverAble2Shell chain, and it lists no victim count, no named group and no indicators of compromise. Watch N-able’s advisory for detection guidance.

Why should a website owner care about an MSP console?

The console your MSP or host uses to manage your server can usually touch everything on it. Most SiteGuarding readers do not run N-central themselves. Their managed service provider, IT contractor or hosting company might, and the N-central Agent sits on the machines it manages. That can include the server running your WordPress or Joomla site.

The precedent is Kaseya VSA in July 2021. Kaseya said fewer than 60 on-premises customers were directly hit, but up to 1,500 downstream businesses felt it. Nothing reported so far puts the N-central story anywhere near that scale. The lesson is the shape of the risk: one console, many victims.

RMM platforms exist to push scripts, deploy software and open remote sessions across many endpoints from one place. That is the product working as designed. It also means a compromised management server can reach files, control panels, database credentials and FTP accounts that never show up in wp-admin. Your security plugin watches the site. It does not watch the agent running beside it with system rights.

Who has to act depends on the deployment. N-able says it has already patched hosted N-central environments. On-premises operators run their own servers and must upgrade them. N-able’s wording is direct: “To keep your environment protected, customers running on-premises N-central deployments should upgrade their servers as soon as possible.”

What is 4EverAble2Shell, and what did the hotfix change?

4EverAble2Shell is a public exploit chain against N-central that security researcher Sean Bales posted on GitHub on November 12, 2026. SecurityWeek described him as a disgruntled researcher. Either way, the code went public before a fix did.

The chain joins two problems. The first is CVE-2026-90436, a critical remote code execution flaw in Apache Axis, a SOAP web services framework. The second is an N-central issue that only matters on deployments where legacy APIs were enabled. Together they end with a shell script running as root on the N-central server. Technical detail belongs in N-able’s advisory, not here.

Attackers did not wait. Threat actors started using the proof of concept within hours of disclosure to install cryptocurrency miners. No group has been named, and the reporting includes no hashes, wallets or victim counts. If the Monday release fell on November 16, as the report’s timing suggests, on-premises servers waited four days for a fix.

The most important fix is simple. Hotfix 3 removes the configuration option for legacy APIs, so they are permanently blocked and nobody can switch them back on. N-able says that defeats the 4EverAble2Shell chain. Any integration that still calls those old endpoints will break with this update. That is a fair trade.

Bales kept going. Shortly after N-able announced the fixes, he published technical details on 24 more N-central vulnerabilities, which he says are patched and should not be exploitable on current deployments.

That claim holds only for a server, and its Agents and Probes, actually running the current release. Detailed write-ups help anyone hunting for unpatched installs, so staying on Hotfix 2 just got riskier. Verify the version instead of assuming it.

Do Agents and Probes still need an upgrade after the server is patched?

Yes, and this is the step most likely to get skipped. N-able’s guidance covers everyone: “All customers, hosted and on-premises, must upgrade all of their Agents and Probes to the latest version to be fully protected. Agents and Probes that are not upgraded are susceptible to impersonation.”

That second sentence is the one to note. A hosted customer’s server may already be patched, yet that customer can still have old Agents in the field, and those Agents can be impersonated. N-able does not spell out the mechanics. The plain reading is that the console’s trust in managed devices can be abused until every component is current.

Hotfix 3 tightens that trust model in three ways: stronger Agent verification, better management of inactive Agents, and a new rule that devices must be identified before they can connect to N-central at all. Expect some devices to drop off after the upgrade until someone approves them.

Approval is where teams often undo their own hardening. When fifty devices show up as unidentified, the temptation is to bulk-approve them and move on. Reconcile them first. Every unknown, duplicate or newly disconnected device should map to a named asset owner. A device nobody can account for is exactly what the new check was built to catch.

Found a miner? Treat it as a root compromise

If an on-premises N-central server shows mining activity, assume the attacker had root and respond on that basis. The miner proves code execution. It does not prove that mining was the only thing the attacker did. A root shell can add persistence, read stored credentials and switch off security tooling. On an RMM server, those credentials may unlock every endpoint it manages.

In our incident work, the same pattern keeps repeating. The client deletes the miner, CPU usage drops and everyone relaxes. A week later, a cron entry or SSH key the attacker left behind brings it back. Clean it up properly:

  • isolate the host and preserve memory and logs before you clean anything
  • hunt for persistence: new users, scheduled tasks, services and keys
  • after containment, rotate administrative and service credentials, including anything N-central stores for managed devices
  • check the managed endpoints, starting with web servers, for new scripts or software pushed from the console

Audit log tampering is one of the 17 bug classes, so a clean N-central audit trail does not prove the server is clean. Pull network logs, identity provider records, endpoint telemetry and anything shipped to remote storage, and build the timeline from those sources.

Is Confluence in the same CVE-2026-90436 story?

Partly. Attackers are also using the Apache Axis flaw, CVE-2026-90436, against Atlassian Confluence, but Confluence is a separate product with a separate fix. Rapid7 reported that as of November 13 attackers had turned the Axis bug on Confluence instances with the Remote API (XML-RPC and SOAP) setting enabled.

Atlassian fixed the issue in Confluence 9.2.28, released November 9, three days before the N-central chain went public. The vulnerable setting is old. Atlassian says: “Please note that this setting was turned off by default for new installations starting in Confluence 3.0. This feature was fully removed in Confluence 10.0.”

The exposed systems are therefore aging Confluence servers below 10.0, unpatched, with Remote API switched on years ago and never turned off. If you run a company wiki on Confluence, check the version and that setting today. This is a different bug from the one in our Atlassian Data Center patch guidance, and patching N-central does nothing for Confluence.

What should you ask your host or MSP today?

If someone else manages your server, send them a short email today. You do not need to know N-central to ask the right questions:

  1. Do you use N-able N-central to manage our server, and is it hosted by N-able or on-premises?
  2. Is the N-central server on 2026.4 Hotfix 3?
  3. Has every Agent and Probe that can reach our site’s server been upgraded?
  4. Were legacy APIs enabled before Hotfix 3 removed the option, and could anyone reach those endpoints from the internet?
  5. Have you checked our server for new admin users, scheduled tasks, unfamiliar processes or mining activity since November 12?
  6. If you found anything, which credentials have you rotated, and do our site, database and FTP passwords need changing too?

A vague “we’re fine” does not answer question 3. Ask for the version. If the reply raises doubts, scan your site files for changes you did not make. Our website antivirus looks for injected code and backdoors.

The same rule applied in our piece on checking your host and rotating secrets after PHP2Shell: when the flaw sits below your site, the fix starts with your provider and ends with your passwords.

FAQ

What is N-central 2026.4 Hotfix 3?

It is N-able's critical security update for its N-central RMM platform. It patches 17 zero-days, hardens authentication and Agent communication, adds a device identification requirement and removes the legacy API option.

What is 4EverAble2Shell?

It is a public exploit chain that researcher Sean Bales released on GitHub on November 12, 2026. It combines Apache Axis flaw CVE-2026-90436 with an N-central legacy API issue to run a script as root, and attackers used it to deploy miners.

Who needs to patch N-central, hosted or on-premises?

Both, in different ways. N-able says it has already patched hosted servers. On-premises operators must upgrade their own servers, and every customer must upgrade all Agents and Probes.

Do I need to upgrade N-central Agents and Probes?

Yes. N-able says all customers, hosted and on-premises, must upgrade every Agent and Probe. Outdated ones are susceptible to impersonation even after the server is patched.

Is CVE-2026-90436 patched in Confluence?

Yes. Atlassian fixed it in Confluence 9.2.28, released November 9, 2026. Only instances with the legacy Remote API (XML-RPC and SOAP) enabled are exposed, and Confluence 10.0 removed that feature.

Are N-central legacy APIs still available?

No. Hotfix 3 removes the configuration option, so legacy APIs are permanently blocked and cannot be re-enabled.

If your provider’s answers leave you unsure whether your server was touched, our team can clean and harden the site behind it. See SiteGuarding protection packages.