CVE-2026-59987: avahi · Reachable Assertion
Affects avahiSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium : upgrade to 0.9-rc5 when convenient.
Data as of 20 Nov 2026, 18:14 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.5 |
|---|
- Patch
- Available – fixed in 0.9-rc5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade avahi to 0.9-rc5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| avahiavahi | Affected
| Fixed in
|
Description
Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. In 0.9-rc4 and earlier, org.freedesktop.Avahi.Server.RecordBrowserNew accepts a domain-name value that avahi_is_valid_domain_name considers valid even though avahi_normalize_name_strdup cannot normalize it. The resulting null key reaches the key assertion in dbus_prepare_record_browser_object. A local low-privileged D-Bus client can trigger the mismatch and terminate the Avahi daemon, causing denial of service. The issue is fixed in 0.9-rc5.