CVE-2025-59529 | simple protocol server ignores accepts unlimited connections and logs failures without limit

Exp

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-rc2, 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.

Published: 2025-12-18 Last update: 2026-01-16 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-59529 is rated Exploit Available (50/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.06%). Core evidence: 3 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-59529

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗
nvd_ref exploit_tag Exploit-DB ↗
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-59529

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-28 0.05% 0.06% +0.02%
2 2026-05-17 0.05% 0.05% -0.00%
3 2026-04-23 0.05%

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-59529

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 3.6 [email protected]

Weakness enumeration for CVE-2025-59529

OS Trackers for CVE-2025-59529

vendor priority summary link
alpine CVE-2025-59529: 1 source package rows (avahi); 54 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 0, open 54. https://security.alpinelinux.org/vuln/CVE-2025-59529
debian not yet assigned CVE-2025-59529 not yet assigned priority: Debian including 1 source packages (avahi), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2025-59529
redhat medium https://access.redhat.com/security/cve/CVE-2025-59529
suse medium https://www.suse.com/security/cve/CVE-2025-59529/
ubuntu medium CVE-2025-59529 medium priority: Ubuntu including 1 source packages (avahi), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): deferred 7, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2025-59529

Affected software / configurations for CVE-2025-59529

Vendor Product Version Raw CPE
avahi avahi < 0.9 cpe:2.3:a:avahi:avahi:*:*:*:*:*:*:*:*
avahi avahi 0.9 cpe:2.3:a:avahi:avahi:0.9:rc1:*:*:*:*:*:*

References for CVE-2025-59529

cvelogic Threat Intelligence