<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>bunny.net pulls an Armenia CDN node after its hosting provider is breached and reissues TLS certificates · updates</title>
  <link>https://pwn.watch/i/bunny-net-armenia-cdn-node-provider-compromise-oct-2026</link>
  <description>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.</description>
  <language>en</language>
  <lastBuildDate>Thu, 29 Oct 2026 00:00:00 GMT</lastBuildDate>
  <atom:link href="https://pwn.watch/i/bunny-net-armenia-cdn-node-provider-compromise-oct-2026/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>bunny.net pulls an Armenia CDN node after its hosting provider is breached and reissues TLS certificates: bunny.net says reissuance of managed custom-domain TLS certificates with new private keys is going in batches and should finish by the end of Oct 31; no new evidence of access to its server.</title>
    <link>https://pwn.watch/i/bunny-net-armenia-cdn-node-provider-compromise-oct-2026</link>
    <guid isPermaLink="false">https://pwn.watch/i/bunny-net-armenia-cdn-node-provider-compromise-oct-2026#2026-10-29-8c052166</guid>
    <pubDate>Thu, 29 Oct 2026 00:00:00 GMT</pubDate>
    <category>medium</category>
    <description>&lt;p&gt;&lt;a href=&quot;https://status.bunny.net/incidents/p6gf1by9kr7m&quot;&gt;Source&lt;/a&gt;&lt;/p&gt;</description>
  </item>
  <item>
    <title>bunny.net pulls an Armenia CDN node after its hosting provider is breached and reissues TLS certificates: bunny.net discloses that an infrastructure provider reported unauthorized access involving third-party server management software; bunny.net's Armenia CDN node ran on a server from that provider. It stopped routing traffic through it within 20 minutes, wiped and removed the server, and revoked and reissued all TLS certificates for b-cdn.net and bunny.run.</title>
    <link>https://pwn.watch/i/bunny-net-armenia-cdn-node-provider-compromise-oct-2026</link>
    <guid isPermaLink="false">https://pwn.watch/i/bunny-net-armenia-cdn-node-provider-compromise-oct-2026#2026-10-28-6f14e5a5</guid>
    <pubDate>Wed, 28 Oct 2026 00:00:00 GMT</pubDate>
    <category>medium</category>
    <description>&lt;p&gt;&lt;a href=&quot;https://status.bunny.net/incidents/p6gf1by9kr7m&quot;&gt;Source&lt;/a&gt;&lt;/p&gt;</description>
  </item>
</channel>
</rss>
