N-able releases hotfix for some leaked N-central zero-days after taking hosted servers offline

Hosted N-central servers have been upgraded, but on-premises customers must install the HF2 hotfix themselves while a threat intelligence firm reports active probing.

SecurityPublished Updated

Correction, . An earlier version said N-able had not answered questions about the researcher's claim that it ignored earlier disclosures. N-able's statement, carried in BleepingComputer's report, says the claim is inaccurate; we have also corrected the headline, which implied the hotfix covers every leaked flaw.

What happened
N-able released N-central 2026.4 HF2 to fix some of the zero-day flaws a researcher published without warning, after pulling its hosted service offline.
What’s new
N-able says all hosted N-central servers are now upgraded, and it is urging on-premises customers to install the hotfix as soon as possible.
Why it matters
N-central gives IT teams and managed service providers central control over client networks, so working exploits could expose many downstream organisations.

N-able has shipped security hotfixes for its N-central remote monitoring and management platform. The release follows a weekend public disclosure of zero-day vulnerabilities that led the company to shut down its hosted service across the Americas, Europe and Asia-Pacific.

N-central is used by IT departments and managed service providers to monitor and manage client networks and devices from a web console. Remote access tools like this are a frequent target for attackers, TechCrunch notes, because they can open broad access to a company's network and data.

From disclosure to hotfix in two days

The flaws were published late on Sunday, November 8, in a GitHub repository called Able2Shell that contained proof-of-concept exploits; TechCrunch describes them as dozens of zero-day bugs. N-able took its hosted N-central environment offline on Monday, November 9. It also advised customers running their own servers to disconnect them until further notice.

The company then released N-central 2026.4 HF2. According to BleepingComputer, the update fixes some of the leaked zero-days, including the ones N-able described as most critical. These include XXE and OGNL injection flaws, a path-traversal remote code execution bug and several local privilege escalation issues. In an update on Tuesday, November 10, N-able said every hosted N-central server in all regions had been upgraded. It strongly recommended that on-premises customers upgrade and follow its published guidance before restoring normal access.

The researcher said the bugs affect a pre-release build, N-central Appliance 2026.4.0.31, and probably most earlier versions too. The disclosed issues include remote code execution, authentication bypass, credential disclosure, arbitrary file writes and cross-site scripting. One demonstrated chain uses an unauthenticated XXE flaw in the service-import feature to reach command execution. It can also create an administrator account with credentials the attacker chooses.

No confirmed exploitation, but probing reported

N-able told TechCrunch it has no evidence of successful exploitation against any customer environment. A company spokesperson did not say whether N-able has a way to check, such as through server logs.

Threat intelligence firm Defused, quoted by BleepingComputer, said it had seen probing aimed at the disclosed zero-days within 24 hours, including anonymous agent sessions, appliance configuration pulls and unauthenticated access to the remote control endpoint. Defused urged administrators to take servers offline immediately.

Shadowserver's scans suggest many operators have already acted. The nonprofit counted 1,338 internet-exposed N-central servers on Monday and just over 148 by the time of BleepingComputer's report.

A disputed disclosure

BleepingComputer names the researcher as Sean Bales; TechCrunch gives the name as Ben Bales. He told BleepingComputer he released the bugs without notifying N-able because the company had allegedly not patched vulnerabilities he reported in a different N-able product five to six months earlier. Those earlier reports included two remote code execution bugs and a privilege escalation flaw. In a statement carried in BleepingComputer's report, N-able said claims that it ignored responsible disclosure from the researcher are inaccurate and that the newly published vulnerabilities were not responsibly disclosed through its established reporting channels. The statement does not say whether the researcher's earlier reports on a different product were patched.

Several questions remain open. BleepingComputer's wording indicates HF2 covers some, not necessarily all, of the leaked flaws. N-able did not tell TechCrunch whether it can check for exploitation, for example through server logs.