Researcher Discloses 33 Alleged N-central Zero-Days in “Able2Shell”

· Original article ↗

Summary

Researcher Sean Bales disclosed 33 alleged N-central zero-days as “Able2Shell,” with four chains reportedly enabling privileged code execution. N-able took hosted services offline and urged on-premises customers to shut down pending a hotfix.

Key points

  • Sean Bales publicly disclosed 33 alleged N-central vulnerabilities under the name “Able2Shell”; no CVE identifiers had been assigned.
  • The disclosed flaw classes include authentication bypass, credential disclosure, arbitrary file writes, directory traversal, XSS, XXE, and remote code execution.
  • Four described exploit chains reportedly lead to code execution as the nable user or root, or enable creation of an administrator account.
  • The flaws were tested on pre-release N-central Appliance 2026.4.0.31; Bales believes most or all may also affect earlier generally available versions.
  • N-able took its hosted N-central classic environment offline and advised on-premises customers to shut down their servers until further notice.
  • N-able had not observed active exploitation of these specific vulnerabilities and estimated a hotfix for November 10, 2026, pending validation.
  • The advisory recommends reviewing authentication and audit logs, checking for unauthorized administrator accounts, and waiting for explicit vendor confirmation before restoring service.

Article Details

Vulnerability Types
  • Authentication bypass
  • Credential disclosure
  • Arbitrary file write
  • Directory traversal
  • Cross-site scripting (XSS)
  • XML External Entity (XXE) injection
  • Remote code execution (RCE)
  • Privilege escalation
Severity
Critical and high; individual vulnerability ratings were not specified.
Affected Versions
  • N-able N-central Appliance 2026.4.0.31
  • Earlier N-able N-central versions (the researcher believes most or all are affected)
Exploitation Status
not_reported
Exploit Availability
public_poc
Patch Status
unavailable
Workarounds
  • Take on-premises N-central servers offline until N-able confirms it is safe to restore service.
  • Hosted N-central classic environments are offline; monitor N-able status updates.
  • Use the accessible Ecoverse services as alternative management paths where necessary.

MITRE ATT&CK

People

Vendors

Products

Industries

Related Articles