CVE-2026-24401 is an uncontrolled-recursion flaw (CWE-674) in avahi-daemon 0.9-rc2 and earlier: anyone on the local link can send an unsolicited mDNS response with a CNAME that points to itself, the daemon recurses until the stack runs out and crashes. NVD scores it 6.5; v0.9-rc3 fixes it.
Vulnerability summary
CVSS base score
6.5
Medium severity
EPSS score (FIRST)
0.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2026-24401 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Avahi (avahi-daemon) | cpe:2.3:a:avahi:avahi:*:*:*:*:*:*:*:* | 0.9-rc2 and earlier, including 0.8 (fixed upstream in v0.9-rc3, commit 78eab31; backported in Buildroot avahi 0.8 patch 0016) |
What does this mean for affected devices?
CVE-2026-24401 is a remote crash of the Avahi mDNS/DNS-SD daemon. According to NVD, 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", for example h.local as a CNAME for h.local. This causes unbounded recursion in lookup_handle_cname and exhausts the stack. NVD classifies it as CWE-674 and scores it CVSS v3.1 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H), the same as GitHub's CNA score.
The precondition matters for triage. NVD says the flaw affects record browsers where AVAHI_LOOKUP_USE_MULTICAST is set explicitly, "which includes record browsers created by resolvers used by nss-mdns". On a device that resolves .local host names through nss-mdns, or runs any application that browses for services, the daemon is in that state during normal operation. The attacker only needs to send multicast DNS to UDP port 5353 on the same link, which on a guest Wi-Fi, a shared building network or a flat OT segment is anyone attached to it.
Avahi's advisory GHSA-h4vp-5m8j-f6w3 lists versions up to v0.9-rc2 as vulnerable and v0.9-rc3 as patched; the fix is commit 78eab31, which adds loop detection to the CNAME lookup. For firmware the backport is the usual route because 0.8 is still the last final release. Buildroot's avahi package applies the commit to Avahi 0.8 as 0016-core-fix-uncontrolled-recursion-bug-using-a-simple-loop-detection-algorithm.patch and marks the CVE as ignored for its CVE scan. Our guide to Yocto and Buildroot SBOMs shows how to read the patch list from a build, and firmware diffing and patch analysis shows how to confirm the fix in a vendor binary.
Distribution coverage is uneven. The Debian security tracker lists bookworm (0.8-10+deb12u1) and trixie (0.8-16) as vulnerable, marked as a minor issue without a DSA, with only unstable fixed in 0.8-18. A product based on a stable Debian release therefore needs its own patch.
As of 2026-11-16 the CVE is not in the CISA KEV catalog (version 2026.11.13), and FIRST EPSS gives it 0.00373 (32nd percentile) in its 2026-11-15 dataset. Our Avahi and mDNS/DNS-SD vulnerabilities guide ranks it, with the related CNAME crash CVE-2025-68468, ahead of the local flaws such as CVE-2021-3468 and CVE-2023-38469, because anyone on the device's network can stop its discovery. Until a patched build ships, restrict avahi-daemon to trusted interfaces with allow-interfaces or deny-interfaces and block UDP 5353 on untrusted segments.
Evidence
- Recursive CNAME in an unsolicited mDNS response causes unbounded recursion in lookup_handle_cname in avahi 0.9rc2 and below; CWE-674; CVSS v3.1 6.5 (NVD and CNA). — NVD
- Avahi advisory GHSA-h4vp-5m8j-f6w3 lists <= v0.9-rc2 as vulnerable and v0.9-rc3 as patched (commit 78eab31). — Avahi GHSA-h4vp-5m8j-f6w3
- Buildroot builds Avahi 0.8 with patch 0016 (upstream 78eab31) and ignores CVE-2026-24401 in its CVE scan. — Buildroot package/avahi/avahi.mk
- Debian bookworm 0.8-10+deb12u1 and trixie 0.8-16 vulnerable (no-dsa, minor issue); unstable fixed in 0.8-18. — Debian Security Tracker
- Not in the CISA KEV catalog version 2026.11.13 (checked 2026-11-16). — CISA KEV
- EPSS 0.00373, 32nd percentile, FIRST dataset of 2026-11-15. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Who can trigger CVE-2026-24401?
Anyone who can send multicast DNS to the device on its local link. NVD scores the attack vector as network with no privileges and user interaction required (UI:R), and its description limits the flaw to record browsers with AVAHI_LOOKUP_USE_MULTICAST set, which includes those created by nss-mdns resolvers (per NVD).
Which Avahi version fixes CVE-2026-24401?
v0.9-rc3, through commit 78eab31. Avahi's advisory GHSA-h4vp-5m8j-f6w3 lists v0.9-rc2 and earlier as vulnerable (per the Avahi advisory).
Is a device on Avahi 0.8 affected?
Yes, unless the fix was backported. Buildroot carries it as patch 0016 on Avahi 0.8, while Debian bookworm and trixie are listed as vulnerable (per Buildroot avahi.mk and the Debian security tracker).
How can I reduce exposure before a patched firmware ships?
Bind avahi-daemon to trusted interfaces only and block UDP port 5353 on guest or shared networks, so untrusted hosts cannot reach the daemon with mDNS responses. As of 2026-11-16 the CVE is not in CISA KEV and its EPSS is 0.00373 (per CISA KEV and FIRST EPSS).
Questions about this page?