Breachpwn.watchEnergy & utilitiesPublic sector

    bunny.net pulls an Armenia CDN node after its hosting provider is breached and reissues TLS certificates

    Teaser from the source

    On Oct 28 2026, CDN company bunny.net said one of its infrastructure providers reported unauthorized access involving third-party server management software. One bunny.net CDN node, in Armenia, ran on a server from that provider. bunny.net stopped routing traffic through it within 20 minutes, wiped it and removed it for good. Neither bunny.net nor the provider has found evidence the node was accessed, but bunny.net can't rule it out; if it was, cached CDN content, Pull Zone configurations and TLS certificates stored on that server could have been exposed. bunny.net revoked and reissued certificates for its own b-cdn.net and bunny.run domains and is reissuing managed custom-domain certificates with new private keys, expected to finish by the end of Oct 31. It says no account data was on the server and no internal systems were affected.

    This is the RSS-feed teaser. Read the full article at the original source.

    Read at pwn.watch

    Source: https://pwn.watch/i/bunny-net-armenia-cdn-node-provider-compromise-oct-2026

    ID