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

Published Dec 18, 2025
·
Updated

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 CLIENTSMAX is defined, serverwork() unconditionally accept()s and clientnew() always appends the new client and increments nclients. 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.

Affected Software

5 affected components
avahi<=0.9-rc2
Microsoft cbl2 avahi 0.8-4
Microsoft azl3 avahi 0.8-5
Avahi Avahi<0.9
Avahi Avahi=0.9-rc1

Remediation

Event History

Dec 18, 2025
CVE Published
via MITRE·08:25 PM
Data Sourced
via MITRE·08:25 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Dec 21, 2025
Data Sourced
via Microsoft·01:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·01:02 AM
Affected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-59529?

CVE-2025-59529 has been classified with a high severity due to its potential to allow local denial of service (DoS) attacks.

2

How do I fix CVE-2025-59529?

To mitigate CVE-2025-59529, upgrade to a version of Avahi later than 0.9-rc2 which addresses the issue.

3

What is the impact of CVE-2025-59529?

The impact of CVE-2025-59529 allows attackers to exploit the vulnerability by making unlimited connections to the simple protocol server, leading to service disruption.

4

Which versions of Avahi are affected by CVE-2025-59529?

Avahi versions up to and including 0.9-rc2 are affected by CVE-2025-59529.

5

Is CVE-2025-59529 specific to any operating systems?

CVE-2025-59529 is not specific to any operating systems; it affects any system running the vulnerable versions of Avahi.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203