Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The zeroconf package before 0.149.12 is vulnerable to memory exhaustion. An unauthenticated host on the local network can flood it with truncated mDNS queries, using spoofed source addresses, which can exhaust memory and degrade CPU use. Upgrade to zeroconf 0.149.12 or later; the source lists no workaround other than restricting mDNS traffic to trusted network segments.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.5 | Medium | 3.1 | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0037, the 31st percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:59 UTC First seen by agentprime
- 31 Oct 2026, 14:59 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-9663-mqmp-p9mm
- OSV: GHSA-9663-mqmp-p9mm
- github.com/python-zeroconf/python-zeroconf/security/advisories/GHSA-9663-mqmp-p9mm
- github.com/python-zeroconf/python-zeroconf/pull/1751
- github.com/python-zeroconf/python-zeroconf/commit/b22c8ff19c66c68907d220a4823c0950f4fa93f7
- github.com/python-zeroconf/python-zeroconf