bunny.net reports a second provider security incident: unauthorised SSH keys were added to a server hosting an out-of-rotation CDN node in Pakistan; it is reissuing TLS certificates again
bunny.net said on its status page, in an update posted 18 November 2026 at 12:25 UTC (20:25 AWST), that on 17 November an infrastructure provider reported unauthorised access involving third-party server management software, and that one bunny.net CDN node in Pakistan was hosted on an affected server (source: bunny.net).
Bunny says the node had already been out of traffic rotation for over a week due to network maintenance and was not serving requests, and that within 8 minutes of the alert it removed the server from its system, preserved the security logs, securely wiped the server, revoked its access to other systems and permanently removed it (source: bunny.net).
Bunny says its investigation confirmed that unauthorised SSH keys had been added to the server through the provider's virtualization layer; it found no evidence the keys were used, but says it cannot rule out that data was accessed or copied through the virtualization layer (source: bunny.net).
If data was accessed, Bunny says the potentially exposed information would have been temporarily cached CDN content, Pull Zone configurations and TLS certificates stored on that server; no other customer data, including bunny.net account data, was on the server and no internal systems were affected (source: bunny.net).
As a precaution Bunny says it revoked and reissued all TLS certificates for its platform domains (b-cdn.net and bunny.run) and is reissuing managed TLS certificates for custom domains, expecting to finish within 24 hours (source: bunny.net). Bunny calls this the second of two security incidents involving separate infrastructure providers in recent weeks and says it is reviewing and reducing its reliance on third-party cloud platforms, which host a small portion of its CDN (source: bunny.net).
Bunny does not name the provider. The status page showed the incident as Monitoring.
- Product
- bunny.net CDN (one CDN node in Pakistan on a third-party provider server)
- Versions
- n/a — security incident
- Exploited in Australia?
- unknown
- Patch to
- Per bunny.net: no action is needed for customers using managed TLS certificates. Customers who manage their own TLS certificates are advised to revoke and reissue them with new private keys as a precaution.
