Sean Bales says publishing 33 alleged zero-days for N-able's N-central platform forced the vendor to move faster. That argument deserves a hard look, because the evidence in this case points the other way. Bales published proof-of-concept code on November 9 without, by his own confirmation to Infosecurity, disclosing any of the vulnerabilities to N-able. The company says it had no notice through its established channels.

The damage was visible almost immediately. N-able took hosted N-central offline as a precaution and told on-premises customers to keep their servers offline until patched. WatchTowr saw exploitation attempts against its N-central honeypots overnight, according to a Beazley Security advisory updated November 10. Those were decoys, not customer networks, but they show scanners moving on the published code within hours. For a remote monitoring and management platform, which sits with privileged access across many client environments, that is the scenario a responsible disclosure process exists to prevent.

N-able's response is not flawless. Its hotfix addresses seven CVEs, and the release notes and company statement do not explain how those map to the 33 Able2Shell issues. PoC code for all 33 remains public. Customers are left without a clear account of what is fixed and what is still exposed, and remote control stays disabled until a future fix. Those are real gaps, and N-able should close them quickly and plainly.

Still, the disagreement is not a close call. John Pagliuca's statement that publishing exploit code before customers can act "hands attackers a head start" describes what happened here. Bales's claim that disclosure forces vendors to fix faster rests on a model that assumes the vendor has been given a fair chance first. Publishing without that chance removes the window in which customers could be protected at all. Researchers who find serious flaws should report them privately, give a reasonable deadline, and publish only once a fix or mitigation exists.