Home/Blog/N-central Legacy API exploit targets the HF2 build
blog

N-central Legacy API exploit targets the HF2 build

November 12, 2026 · Security News

Cover image for the N-central Legacy API exploit: on-premise build 2026.4.1 HF2, with the Legacy API marked as the setting N-able told customers to disable.

The N-central Legacy API exploit claims published on November 12, 2026 target on-premise build 2026.4.1 HF2, the update N-able shipped two days earlier for Able2Shell. A break-in on that console is a path onto every PC an MSP manages from it. Check whether the Legacy API is on, and whether it answers from the internet.

Key takeaways

  • On November 12, 2026 N-able said it was investigating new proofs of concept against on-premise N-central 2026.4.1 HF2, build 2026.4.1.26, in the Americas, APAC, and Europe. Hosted N-central is out of scope.
  • N-able's initial assessment says the server issue needs the Legacy API enabled and exposed to the internet. The API is off by default and is not recommended.
  • Sean Bales describes 4EverAble2Shell as unauthenticated root code execution on the server and Agent2Shell as SYSTEM commands on managed Windows agents when the attacker knows the appliance ID. N-able has not confirmed the root-RCE wording.
  • Previdian reported 4EverAble2Shell probing from a single source address within hours, and watchTowr reported the same class of probes. Successful exploitation was unconfirmed. One chain used Apache Axis CVE-2026-90436 (CVSS 9.8, patches November 6), then a curl download of a shell script.

What did N-able say on November 12?

N-able’s advisory on Thursday, November 12, 2026 says the company is investigating a new public disclosure against on-premise N-central 2026.4.1 HF2, build 2026.4.1.26. Hosted N-central sits outside this issue. The notice names N-central On-premise in the Americas, APAC, and Europe: self-hosted copies of the remote monitoring and management console MSPs and internal IT use to inventory PCs, push software, and run tasks.

N-able’s initial assessment centers on configuration. The vendor said the server issue depends on a non-default setup in which the Legacy API is turned on and exposed to the public internet. The Legacy API is turned off by default and is not recommended.

The advisory is an investigation notice. N-able told on-premise customers to turn the Legacy API off if it is still enabled. N-able can revise the scope when the review ends.

Sean Bales, the independent researcher who disclosed Able2Shell earlier the same week, is also the source of the new claims. The November 12 reporting calls those claims 4EverAble2Shell and Agent2Shell.

  • Week of November 9, 2026: Sean Bales discloses the Able2Shell set.
  • November 10: N-able ships 2026.4 Hotfix 2, build 2026.4.1.26, as the fix for that set.
  • November 12: Bales publishes 4EverAble2Shell and Agent2Shell and says both work on build 2026.4.1.26. N-able opens a review. Previdian and watchTowr report probes the same day.

An operator who installed HF2 on November 10 is running the version Thursday’s notice names. A matching build shows the Able2Shell fix is installed. It does not show whether anyone reached the server.

The precondition N-able named is a Legacy API reachable from the public internet. External network penetration testing checks whether the management plane answers from the open internet, including through a proxy left in front of it.

Does the N-central Legacy API exploit survive Hotfix 2?

Hotfix 2 closes Able2Shell. Sean Bales says the N-central Legacy API exploit claims, 4EverAble2Shell and Agent2Shell, still apply to that same build, 2026.4.1.26. Keep HF2 if you already have it.

A server running anything older than 2026.4.1 HF2 is still exposed to Able2Shell. A server on 2026.4.1.26 has the Able2Shell fix and is the build named in the new disclosure. As of November 12, the reporting describes no newer build that N-able presents as a fix for 4EverAble2Shell or Agent2Shell. The review was still open that day.

4EverAble2Shell is the name Bales gave a server flaw he describes as unauthenticated remote code execution as root on on-premise N-central. N-able’s initial assessment limits that server issue to cases where the Legacy API is enabled and reachable from the public internet. N-able has not confirmed the root remote-code-execution description.

Agent2Shell is the second proof of concept, also from Bales, also reported against build 2026.4.1.26. He describes a chain of more than 10 zero-day bugs that can run commands on managed Windows agents as NT AUTHORITY\SYSTEM when the attacker already knows the target appliance ID.

The server claim and the agent claim are different jobs. 4EverAble2Shell is about the N-central host. Agent2Shell is about commands on Windows machines that host already manages, and only after the attacker can name that appliance.

Many companies never licensed N-central themselves. Their IT provider runs it. Root on that box would let an attacker push software to the customers the MSP watches from it. Probing was reported, and no breach was confirmed.

Who is already probing, and was anyone broken into?

Scanning for 4EverAble2Shell began within hours of the proof of concept. When Previdian spoke to The Hacker News, it had no evidence of successful exploitation.

Ryan Dewhurst, founder and CEO of Previdian, told reporter Ravie Lakshmanan that targeted probing against 4EverAble2Shell had been seen within hours of the proof-of-concept release. Previdian described activity from a single source address. That address is in the original reporting. Copy it from there if you are adding a block-list entry.

watchTowr posted on X the same day that it was seeing 4EverAble2Shell probes against N-central builds with the Legacy API enabled. Previdian specified a single address. watchTowr did not publish a count, so the two reports are not a wide set of confirmed intrusions.

The chain Previdian described had three beats: initial code execution through Apache Axis CVE-2026-90436, an attempt to reach root with 4EverAble2Shell, then a curl request that downloaded a shell script. Seeing only the first request in a log is not the same as seeing all three.

CVE-2026-90436 is an Apache Axis flaw with a CVSS score of 9.8. Apache’s patches for Axis were released on November 6, 2026. Dewhurst called the activity the first documented exploitation attempts against CVE-2026-90436. Build 2026.4.1.26 does not stand in for that Axis update. Apply the November 6 fix on the host that actually runs Axis, or on a service in front of N-central that runs Axis. The reporting attaches the Axis bug to one observed chain. It does not say every N-central server ships a vulnerable Axis build.

Where that chain looks complete, move to threat hunting. On the N-central host, collect process lineage, authentication and API logs, and a record of what the console pushed to agents in the same hours. Export those logs before a rebuild.

What should an on-premise N-central admin do today?

On-premise customers in the Americas, APAC, and Europe have a short list. Hosted customers can treat this specific issue as out of scope.

Disable the Legacy API now if the on-premise console still has it enabled. In the console, find the Legacy API control the November 12 advisory names, set it to disabled, and save. Sign out and back in, then read the control again so a cached screen does not show the old value.

Next, prove the service does not answer from the internet. From a network outside the office, a phone hotspot works, request the management hostname and any Legacy API URL your scripts still call. You want a timeout, a refusal, or a block page. A login form or an API reply means a firewall rule, a reverse proxy, or an old port forward is still publishing the box. Repeat the check against the public address, not only the internal one.

Factory default and the running config are different records. Scripts, billing hooks, and third-party tools keep calling an old interface after the vendor has stopped recommending it. Read the live setting.

  • Confirm the installed build is 2026.4.1 HF2, numbered 2026.4.1.26. Anything older is still exposed to Able2Shell. This build is also the one the new proofs of concept name.
  • Keep the management interface off the public internet. Place the console behind a VPN or a short allow list of administrator addresses.
  • If Apache Axis runs on the host or in front of it, install Apache’s November 6, 2026 fix for CVE-2026-90436. The N-central hotfix does not include that patch.
  • Review the N-central host for unexpected root or administrator activity since November 12, and for curl or wget starting a shell. Copy web and application logs off the box before you change it again.
  • On managed Windows agents, look for command execution you did not schedule, especially as NT AUTHORITY\SYSTEM, in that same window. Agent2Shell, as described, needs the appliance ID. If logs show that ID was retrieved from outside, or that the console itself was reached, extend the review to every agent that console manages.
  • If the console looks compromised, treat downstream customers as in scope. The RMM can push code. Compromised server recovery then has to cover the endpoints, with a customer-by-customer check of what was deployed after the first suspicious login.

Still open on November 12: whether a further hotfix follows the review, how many on-premise servers leave the Legacy API exposed, and whether any probe reached code execution. The reporting that day showed probing and did not confirm a successful intrusion. Read N-able’s advisory again before you treat that status as current.

FAQ

Is every N-central server vulnerable to 4EverAble2Shell?

N-able's initial assessment says the server issue depends on the Legacy API turned on and exposed to the public internet. Default-off installs and hosted deployments sit outside that description, and N-able had not finished its review on November 12.

Are N-able hosted or cloud N-central customers affected?

N-able said hosted environments are not affected. The named scope is on-premise N-central in the Americas, APAC, and Europe.

Does installing 2026.4.1 HF2 mean I am safe from these new claims?

Build 2026.4.1.26, released November 10, 2026, fixes Able2Shell. Bales says 4EverAble2Shell and Agent2Shell work against that same build, and no later fix build was described on November 12.

What does Agent2Shell require before it can run commands as SYSTEM?

As described, Agent2Shell chains more than 10 zero-day bugs to run commands on managed Windows agents as NT AUTHORITY\SYSTEM, and the attacker must already know the target appliance ID. N-able had not confirmed that claim on November 12.

If that console is how customer PCs receive software, have the server and the agents investigated together. SafetyBis can put that on the clock with an emergency incident response retainer.


← All articles

get in touch

Tell us what you're running

Scoping is free. We reply within one business day, and under 30 minutes for active incidents.