CVE-2026-24401Avahi has Uncontrolled Recursion in lookup_handle_cname function
Updated under an hour ago ()
Does this affect you?
It affects avahi. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. In versions 0.9rc2 and below, avahi-daemon can be crashed via a segmentation fault by sending an unsolicited mDNS response containing a recursive CNAME record, where the alias and canonical name point to the same domain (e.g., "h.local" as a CNAME for "h.local"). This causes unbounded recursion in the lookup_handle_cname function, leading to stack exhaustion. The vulnerability affects record browsers where AVAHI_LOOKUP_USE_MULTICAST is set explicitly, which includes record browsers created by resolvers used by nss-mdns. This issue is patched in commit 78eab31128479f06e30beb8c1cbf99dd921e2524, which is part of version 0.9-rc3.
- CVSS
- 6.5 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-674
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- GitHub_M
- NVD analysis
- Modified
- Record last updated
- Oct 23, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
avahi avahi avahi:avahi (from the name) | before 0.9-rc3 | CNA record |
avahi avahi avahi:avahi | before 0.9; 0.9; 0.9 | NVD |
References
- https://github.com/avahi/avahi/security/advisories/GHSA-h4vp-5m8j-f6w3x-refsource-confirm, vendor-advisory
- https://github.com/avahi/avahi/issues/501x-refsource-misc, issue-tracking, patch
- https://github.com/avahi/avahi/commit/78eab31128479f06e30beb8c1cbf99dd921e2524x-refsource-misc, patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.