<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 11:30:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-47180 — Zeroconf: Unbounded recursion in DNS compression-pointer decoder allows LAN-local denial of service</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-47180</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; python-zeroconf&lt;/p&gt;
&lt;p&gt;Zeroconf is a pure Python implementation of multicast DNS service discovery. Prior to 0.149.5, DNSIncoming._decode_labels_at_offset recurses once per DNS-name compression pointer, and a single mDNS packet carrying chained pointers can trigger a RecursionError that escapes DNSIncoming.__init__, causing sustained CPU burn, log flooding, and degraded mDNS-dependent features for unauthenticated hosts on the local link over UDP/5353 (224.0.0.251 / ff02::fb). This issue is fixed in version 0.149.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; python-zeroconf&lt;/p&gt;
&lt;p&gt;Zeroconf is a pure Python implementation of multicast DNS service discovery. Prior to 0.149.5, DNSIncoming._decode_labels_at_offset recurses once per DNS-name compression pointer, and a single mDNS packet carrying chained pointers can trigger a RecursionError that escapes DNSIncoming.__init__, causing sustained CPU burn, log flooding, and degraded mDNS-dependent features for unauthenticated hosts on the local link over UDP/5353 (224.0.0.251 / ff02::fb). This issue is fixed in version 0.149.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-47180</guid>
    </item>
    <item>
      <title>GHSA-9pgc-3ccv-5297 — zeroconf has unbounded recursion in DNS compression-pointer decoder that allows LAN-local denial of service</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-9pgc-3ccv-5297</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: zeroconf&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;`DNSIncoming._decode_labels_at_offset` recurses once per DNS-name compression pointer (RFC 1035 §4.1.4). Pointer cycles and label counts were capped, but the chain length of unique forward pointers was not. A single ~3 kB mDNS packet carrying ~1500 chained pointers drives the recursion past CPython&amp;#39;s default limit, and `RecursionError` was not listed in `DECODE_EXCEPTIONS`, so it escaped `DNSIncoming.__init__` and was logged by asyncio&amp;#39;s default exception handler.&lt;/p&gt;
&lt;p&gt;Any unauthenticated host on the local link (UDP/5353, `224.0.0.251` / `ff02::fb`) can degrade the mDNS listener; that includes a guest on the same Wi-Fi, a compromised IoT device, or a container on a shared bridge. Replaying at a few hertz produces sustained CPU burn and log flooding, and mDNS-dependent features (HomeKit, Chromecast/Matter, AirPlay, printers) degrade while the attack is in flight.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in `zeroconf` 0.149.5 ([PR #1719](https://github.com/python-zeroconf/python-zeroconf/pull/1719)).
Upgrade to `&amp;gt;= 0.149.5`.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no in-process workaround; upgrading is the fix. Otherwise, restrict mDNS (UDP/5353) to trusted Layer-2 segments via AP client isolation, guest-network separation, or host firewall rules.&lt;/p&gt;
&lt;p&gt;### Resources
- [PR #1719](https://github.com/python-zeroconf/python-zeroconf/pull/1719), fix
- [Issue #1713](https://github.com/python-zeroconf/python-zeroconf/issues/1713), public tracking issue
- [RFC 1035 §4.1.4](https://www.rfc-editor.org/rfc/rfc1035#sect…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: zeroconf&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;`DNSIncoming._decode_labels_at_offset` recurses once per DNS-name compression pointer (RFC 1035 §4.1.4). Pointer cycles and label counts were capped, but the chain length of unique forward pointers was not. A single ~3 kB mDNS packet carrying ~1500 chained pointers drives the recursion past CPython&amp;#39;s default limit, and `RecursionError` was not listed in `DECODE_EXCEPTIONS`, so it escaped `DNSIncoming.__init__` and was logged by asyncio&amp;#39;s default exception handler.&lt;/p&gt;
&lt;p&gt;Any unauthenticated host on the local link (UDP/5353, `224.0.0.251` / `ff02::fb`) can degrade the mDNS listener; that includes a guest on the same Wi-Fi, a compromised IoT device, or a container on a shared bridge. Replaying at a few hertz produces sustained CPU burn and log flooding, and mDNS-dependent features (HomeKit, Chromecast/Matter, AirPlay, printers) degrade while the attack is in flight.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in `zeroconf` 0.149.5 ([PR #1719](https://github.com/python-zeroconf/python-zeroconf/pull/1719)).
Upgrade to `&amp;gt;= 0.149.5`.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no in-process workaround; upgrading is the fix. Otherwise, restrict mDNS (UDP/5353) to trusted Layer-2 segments via AP client isolation, guest-network separation, or host firewall rules.&lt;/p&gt;
&lt;p&gt;### Resources
- [PR #1719](https://github.com/python-zeroconf/python-zeroconf/pull/1719), fix
- [Issue #1713](https://github.com/python-zeroconf/python-zeroconf/issues/1713), public tracking issue
- [RFC 1035 §4.1.4](https://www.rfc-editor.org/rfc/rfc1035#sect…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-9pgc-3ccv-5297</guid>
    </item>
    <item>
      <title>PYSEC-2026-3436 — zeroconf has unbounded recursion in DNS compression-pointer decoder that allows LAN-local denial of service</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-3436</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: zeroconf&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;`DNSIncoming._decode_labels_at_offset` recurses once per DNS-name compression pointer (RFC 1035 §4.1.4). Pointer cycles and label counts were capped, but the chain length of unique forward pointers was not. A single ~3 kB mDNS packet carrying ~1500 chained pointers drives the recursion past CPython&amp;#39;s default limit, and `RecursionError` was not listed in `DECODE_EXCEPTIONS`, so it escaped `DNSIncoming.__init__` and was logged by asyncio&amp;#39;s default exception handler.&lt;/p&gt;
&lt;p&gt;Any unauthenticated host on the local link (UDP/5353, `224.0.0.251` / `ff02::fb`) can degrade the mDNS listener; that includes a guest on the same Wi-Fi, a compromised IoT device, or a container on a shared bridge. Replaying at a few hertz produces sustained CPU burn and log flooding, and mDNS-dependent features (HomeKit, Chromecast/Matter, AirPlay, printers) degrade while the attack is in flight.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in `zeroconf` 0.149.5 ([PR #1719](https://github.com/python-zeroconf/python-zeroconf/pull/1719)).
Upgrade to `&amp;gt;= 0.149.5`.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no in-process workaround; upgrading is the fix. Otherwise, restrict mDNS (UDP/5353) to trusted Layer-2 segments via AP client isolation, guest-network separation, or host firewall rules.&lt;/p&gt;
&lt;p&gt;### Resources
- [PR #1719](https://github.com/python-zeroconf/python-zeroconf/pull/1719), fix
- [Issue #1713](https://github.com/python-zeroconf/python-zeroconf/issues/1713), public tracking issue
- [RFC 1035 §4.1.4](https://www.rfc-editor.org/rfc/rfc1035#sect…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: zeroconf&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;`DNSIncoming._decode_labels_at_offset` recurses once per DNS-name compression pointer (RFC 1035 §4.1.4). Pointer cycles and label counts were capped, but the chain length of unique forward pointers was not. A single ~3 kB mDNS packet carrying ~1500 chained pointers drives the recursion past CPython&amp;#39;s default limit, and `RecursionError` was not listed in `DECODE_EXCEPTIONS`, so it escaped `DNSIncoming.__init__` and was logged by asyncio&amp;#39;s default exception handler.&lt;/p&gt;
&lt;p&gt;Any unauthenticated host on the local link (UDP/5353, `224.0.0.251` / `ff02::fb`) can degrade the mDNS listener; that includes a guest on the same Wi-Fi, a compromised IoT device, or a container on a shared bridge. Replaying at a few hertz produces sustained CPU burn and log flooding, and mDNS-dependent features (HomeKit, Chromecast/Matter, AirPlay, printers) degrade while the attack is in flight.&lt;/p&gt;
&lt;p&gt;### Patches
Fixed in `zeroconf` 0.149.5 ([PR #1719](https://github.com/python-zeroconf/python-zeroconf/pull/1719)).
Upgrade to `&amp;gt;= 0.149.5`.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no in-process workaround; upgrading is the fix. Otherwise, restrict mDNS (UDP/5353) to trusted Layer-2 segments via AP client isolation, guest-network separation, or host firewall rules.&lt;/p&gt;
&lt;p&gt;### Resources
- [PR #1719](https://github.com/python-zeroconf/python-zeroconf/pull/1719), fix
- [Issue #1713](https://github.com/python-zeroconf/python-zeroconf/issues/1713), public tracking issue
- [RFC 1035 §4.1.4](https://www.rfc-editor.org/rfc/rfc1035#sect…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-3436</guid>
    </item>
  </channel>
</rss>
