CVE-2026-59987
Description
A flaw was found in Avahi. A local user with low privileges can trigger a Denial of Service (DoS) by sending a specially crafted domain name through the D-Bus interface. A discrepancy between how Avahi validates and normalizes domain names leads to an internal assertion failure, causing the Avahi daemon to terminate unexpectedly.
Statement
This vulnerability is rated as having a Moderate impact because exploitation requires local access with low privileges to the system D-Bus and results solely in a denial of service. By transmitting a domain name string that passes preliminary checks but cannot be normalized, a local user can trigger an assertion failure that aborts the Avahi daemon. This halts multicast DNS hostname resolution and local service discovery until restarted, but it does not permit unauthorized data access, modification, or privilege escalation.
Mitigation
If multicast DNS service discovery is not required, mitigate this issue by stopping and disabling the Avahi daemon:
1. Stop the active service and socket:
# systemctl stop avahi-daemon.socket avahi-daemon.service
2. Disable and mask the service to prevent automatic or D-Bus socket activation:
# systemctl disable avahi-daemon.socket avahi-daemon.service
# systemctl mask avahi-daemon.service
Warning: Stopping and masking avahi-daemon immediately halts mDNS and DNS-SD functionality, which disables automatic network printer and file share discovery as well as .local domain name resolution. Applications or workflows relying on zero-configuration networking may require reconfiguration or restarts.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 5.5 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart
While assertion is good for catching logic errors and reducing the chances of reaching more serious vulnerability conditions, an attacker can still cause a denial of service if they can trigger an assert statement, and if the scope of the assert() extends beyond the attacker's own session. For example, if a server handles multiple simultaneous connections, if an assert() occurs in one single connection that causes all other connections to be dropped, this could be a significant denial of service.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.