boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Thursday, November 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2025-59529

Avahi: simple protocol server ignores accepts unlimited connections and logs failures without limit
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   L   L   L   N  U  N  N  H    5.5   .0024   15.1     —
AFFECTED
  Product  Versions      Fixed
  avahi    <= 0.9-rc5 –  —
TIMELINE
  Sep 17  Reserved by GitHub_M
  Dec 18  Published (CNA: GitHub_M)
  Oct 23  EXPLOIT PUBLISHED — CVE-2025-59529 (avahi). Public exploit reference added.
CWE-400 · CNA: GitHub_M · CVSS v3.1 · 5 references · NVD status: Modified

Description

Avahi is a system which facilitates service discovery on a local network via the mDNS/DNS-SD protocol suite. In versions up to and including 0.9-rc5, the simple protocol server ignores the documented client limit and accepts unlimited connections, allowing for easy local DoS. Although `CLIENTS_MAX` is defined, `server_work()` unconditionally `accept()`s and `client_new()` always appends the new client and increments `n_clients`. There is no check against the limit. When client cannot be accepted as a result of maximal socket number of avahi-daemon, it logs unconditionally error per each connection. Unprivileged local users can exhaust daemon memory and file descriptors, causing a denial of service system-wide for mDNS/DNS-SD. Exhausting local file descriptors causes increased system load caused by logging errors of each of request. Overloading prevents glibc calls using nss-mdns plugins to resolve `*.local.` names and link-local addresses. As of time of publication, no known patched versions are available, but a candidate fix is available in pull request 808, and some workarounds are available. Simple clients are offered for nss-mdns package functionality. It is not possible to disable the unix socket `/run/avahi-daemon/socket`, but resolution requests received via DBus are not affected directly. Tools avahi-resolve, avahi-resolve-address and avahi-resolve-host-name are not affected, they use DBus interface. It is possible to change permissions of unix socket after avahi-daemon is started. But avahi-daemon does not provide any configuration for it. Additional access restrictions like SELinux can also prevent unwanted tools to access the socket and keep resolution working for trusted users.

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
September 17, 2025ReservedReserved by GitHub_M
December 18, 2025PublishedPublished (CNA: GitHub_M)
October 23, 2026EXPLOIT PUBLISHEDEXPLOIT PUBLISHED — CVE-2025-59529 (avahi). Public exploit reference added.

Affected

Affected products and packages — 1 row
VendorProduct / PackageEcosystemVersion introducedFixed
avahiavahi—<= 0.9-rc5—

Weaknesses

CWE-400

References (5)

Related

Authoritative record: CVE-2025-59529 at cve.org

Vendors: avahi

Weaknesses: CWE-400

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2025-59529 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Thursday, November 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.