Skip to main content
CybersecurityVulnerability Management

N-able Bolsters N-central Security with 17 Patch Fixes

Modern tech lab with equipment and devices on a neutral surface and blurred computer screen in background.

17 distinct vulnerabilities — including CVE-2026-129286, described as "SIS GenericFiles version path traversal leads to RCE" — were addressed when N-able released N-central 2026.4 Hotfix 3, a security update the company calls critical.

What N-central 2026.4 Hotfix 3 changes

N-able characterized Hotfix 3 (HF3) as building on protections delivered in HF2 and supplying "further improvements across authentication and access controls, Agent and Probe communications, file handling, server components, legacy APIs, and user management." The company said HF3 removes the configuration option for legacy APIs entirely, an explicit move that "permanently" blocks that mode.

The update also includes improvements across:

  • authentication and access control;
  • Agent, Probe, and appliance security;
  • file and import handling;
  • server hardening; and
  • user management controls.

N-able warned that as of writing, both Remote control functionality and Intune integration are blocked, and that hosted N-central servers are being updated automatically while on‑premise servers must be upgraded by customers.

The technical surface: the 17 CVEs HF3 patches

HF3 addresses a mix of authentication bypasses, missing authorization checks, XML external entity (XXE) vectors, server-side request forgery (SSRF), path traversal that can lead to remote code execution (RCE), and argument-injection issues. The company published a complete list of the fixed vulnerabilities:

  • CVE-2026-129271 - N-central Patch Management Local Privilege Escalation
  • CVE-2026-129272 - MMS3 appliance authentication bypass via predictable passcode
  • CVE-2026-129273 - Audit Export syslog injection allows root command execution
  • CVE-2026-129274 - ServerMMS2 task result submission missing authentication
  • CVE-2026-129275 - repositoryItemGet missing authentication discloses policies
  • CVE-2026-129276 - ServerMMS2 asset data submission missing authentication
  • CVE-2026-129277 - ServerMMS maintenance action read missing authentication
  • CVE-2026-129278 - Take Control audit log tampering without authentication
  • CVE-2026-129279 - Password reset response discrepancy allows user enumeration
  • CVE-2026-129280 - ServerUI SOAP operations missing authorisation checks
  • CVE-2026-129281 - View-only users can set DeviceExecute configuration
  • CVE-2026-129282 - Test email sendmail argument injection, missing authorisation
  • CVE-2026-129283 - N-central custom service import XML external entity injection
  • CVE-2026-129284 - Report Manager and Data Export settings SSRF
  • CVE-2026-129285 - XMPP action response origin validation error
  • CVE-2026-129286 - SIS GenericFiles version path traversal leads to RCE
  • CVE-2026-129287 - SIS repository parser XML external entity injection

Active exploitation: 4EverAble2Shell, Agent2Shell and crypto miners

The HF3 release follows N-able restricting certain N-central features and integrations after disclosure of a set of flaws tracked as 4EverAble2Shell and Agent2Shell. According to the company, those shortcomings "can allow attackers to run arbitrary code as root and gain SYSTEM-level access to Windows systems under specific conditions." The vendor explained that successful exploitation of 4EverAble2Shell depends on legacy API mode being enabled; removing the legacy API in HF3 "plugs the attack vector."

N-able also stated the 4EverAble2Shell vulnerabilities "have since come under active exploitation," with attackers using them to deploy cryptocurrency miners on vulnerable servers.

What this means for technologists, affected enterprises, and hosted customers

  • Technologists and security teams: N-able cautioned that "All customers, hosted and on-premise, must upgrade all of their Agents and Probes to the latest version to be fully protected." The company warned that "Agents and Probes that are not upgraded are susceptible to impersonation," making upgrades a critical step beyond patching servers.
  • Affected enterprises and procurement leads: because Remote control functionality and Intune integration are "blocked" as of writing, organizations should expect some operational disruption and account for those blocks when planning remediation and continuity procedures.
  • Hosted customers: the company said no server-side action is required for Hosted N-central servers because updates are being applied automatically, though hosted customers still must update Agents and Probes to be fully protected.

Independent disclosure and the vendor's position

Independent security researcher Sean Bales disclosed the original flaws and published additional details for 24 CVEs. Bales said in his follow-up that "these are patched vulnerabilities and should not work on the latest patch." N-able's HF3 release explicitly cites the removal of legacy API configuration as a fix that prevents the 4EverAble2Shell exploitation chain from operating when customers are running the updated version.

For on‑premise customers, the immediate, verifiable next steps in the record are straightforward: upgrade N-central servers to HF3 as soon as possible and ensure all Agents and Probes are updated to the latest versions. Hosted customers should confirm Agent and Probe updates even though server-side updates are being applied automatically. HF3 closes a set of critical vectors — including legacy API-dependent chains used in active cryptomining campaigns — but the company’s own notices make clear that incomplete endpoint updates leave environments exposed.

https://thehackernews.com/2026/11/n-able-patches-17-n-central-flaws-as.html