CVE-2026-59987 in Avahi
Summary
by MITRE • 11/20/2026
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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/21/2026
Avahi serves as a critical system-level component for facilitating zero-configuration networking by enabling automatic service discovery on local networks through the multicast DNS and DNS Service Discovery protocol suites. In versions prior to 0.9-rc4, specifically within the implementation of the org.freedesktop.Avahi.Server.RecordBrowserNew interface, a significant input validation flaw exists that allows for a denial of service condition. This vulnerability stems from an inconsistency in how domain names are processed by different internal functions within the Avahi daemon architecture. The core issue lies in the divergence between two specific string handling routines: avahi_is_valid_domain_name and avahi_normalize_name_strdup.
The technical root cause involves a mismatch in validation logic where avahi_is_valid_domain_name accepts certain malformed or edge-case domain-name values as valid inputs from D-Bus clients. However, when these same values are subsequently passed to avahi_normalize_name_strdup for normalization purposes, the function fails to produce a normalized string and instead returns null. This discrepancy creates a state inconsistency within the daemon's processing pipeline because the initial validation step did not anticipate that subsequent normalization could fail or result in an empty pointer.
When this mismatch occurs, the resulting null key is passed further into the dbus_prepare_record_browser_object routine. This function contains a strict assertion designed to ensure that record browser objects are initialized with valid keys. Because the input was deemed valid by the initial check but resulted in a null value after normalization, the assertion fails. In typical daemon implementations, an unhandled assertion failure results in the immediate termination of the process. Consequently, any local low-privileged D-Bus client can exploit this logic error to trigger the assertion and crash the Avahi daemon entirely.
The operational impact of this vulnerability is a complete denial of service for network services relying on Avahi for discovery. Since the Avahi daemon manages the broadcasting and querying of service records across the local area network, its termination disrupts all active service advertisements and lookups. Users may experience sudden loss of connectivity to printers, media servers, or other shared resources that depend on zero-configuration networking protocols. This impact is particularly severe in environments where automatic service discovery is essential for daily operations, as it requires manual intervention or a daemon restart to restore functionality.
From a threat modeling perspective, this vulnerability aligns with CWE-20 Improper Input Validation and CWE-754: Improper Check for Unusual or Exceptional Conditions. The failure lies in the application not properly validating input that leads to an unexpected state (null pointer) which is then treated as fatal by subsequent logic rather than being handled gracefully. In terms of attack vectors, this falls under MITRE ATT&CK technique T1499: Endpoint Denial of Service, specifically leveraging resource exhaustion or process termination via local exploitation. The requirement for a low-privileged D-Bus client indicates that the threat actor does not need administrative privileges to execute the exploit, lowering the barrier for potential abuse by malicious insiders or compromised user-level processes.
Mitigation strategies primarily involve upgrading the Avahi package to version 0.9-rc5 or later, where this validation logic has been corrected to ensure consistency between domain name validation and normalization steps. For systems that cannot be immediately updated, restricting D-Bus access policies can provide a temporary defense-in-depth measure. By configuring polkit rules or systemd socket activation limits to prevent untrusted local users from invoking the RecordBrowserNew method, organizations can mitigate the risk of exploitation until patches are applied. Regular monitoring for unexpected daemon restarts in system logs may also serve as an early detection mechanism for attempted exploits against this vulnerability.