Comment by bobtheborg

  While neither investigation has found any indication of unauthorized access to our server, we cannot completely rule out the possibility.

  If unauthorized access to our CDN node did occur, the potentially exposed information would have been: temporarily cached CDN content, Pull Zone configurations, and TLS certificates stored on that server.

  As an additional precaution, we have revoked and reissued all TLS certificates for bunny. net platform domains (b-cdn. net and bunny. run). Reissuance of managed TLS certificates for custom domains is ongoing and is expected to be completed within the next 24 hours. No action is required from customers using managed certificates. We will post a further update on our status page once this process is complete.

  If you manage your own TLS certificates, we recommend revoking and reissuing them with new private keys as a precaution.

  No other customer data, including bunny. net account data, was stored on the server in question, and no internal systems were affected.

so it seems like the underlying provider potentially allowed, for instance, disk read, that above is what bunny says might have been on disk in this case? Am I reading that right?