CVE-2026-47184: Homeassistant cli · zeroconf has unbounded DNS record cache that allows LAN-local memory exhaustion via multicast flood
Affects homeassistant-cliSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.0.0_2 when convenient.
Data as of 1 Nov 2026, 22:58 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.1.6_23, 1.0.0_2
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.
What to do
Upgrade homeassistant-cli to 1.0.0_2; airshare to 0.1.6_23.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewairsharepkg:brew/airshareOther threats | Affected
| Fixed in
|
Homebrewhomeassistant-clipkg:brew/homeassistant-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in zeroconf version 0.149.6. Users should upgrade to this version to remediate the vulnerability. No in-process workaround exists. Until upgrading, it is recommended to apply network-level restrictions on multicast DNS traffic to mitigate the risk.
Description
The Airshare zeroconf component in homeassistant-cli has an unbounded DNS record cache vulnerability (CVE-2026-47184) that allows any unauthenticated host on the local network to exhaust device memory by flooding multicast DNS responses. This leads to degraded performance or denial of service. The issue is fixed in zeroconf version 0.149.6. No in-process workaround exists, so network-level restrictions on multicast DNS traffic are recommended until upgrading.
References
- github.com/python-zeroconf/python-zeroconf/security/advisories/GHSA-rfg2-pjw2-56x2 (opens in a new tab)
- github.com/python-zeroconf/python-zeroconf/issues/1715 (opens in a new tab)
- github.com/python-zeroconf/python-zeroconf/pull/1718 (opens in a new tab)
- github.com/python-zeroconf/python-zeroconf (opens in a new tab)