VulnerabilityPublished 13 Aug 2026Updated 4 Oct 2026

CVE-2026-48487: zeroconf · Unvalidated rdlength in record payload readers allows LAN-local cache corruption via crafted mDNS packet

Affects homeassistant-cliSource GCVE Database

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.0.0_3 when convenient.

Data as of 1 Nov 2026, 11:03 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.1.6_23, 1.0.0_3

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade homeassistant-cli to 1.0.0_3; airshare to 0.1.6_23.

Affected software

Product	Affected	Fixed in
Homebrewairshare`pkg:brew/airshare`Other threats	Affected >=0.1.5 <0.1.6_23	Fixed in 0.1.6_23
Homebrewhomeassistant-cli`pkg:brew/homeassistant-cli`Other threats	Affected >=0.5.0 <1.0.0_3	Fixed in 1.0.0_3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and the issue is fixed in homeassistant-cli version 0.149.16. Users should upgrade to this version or later to remediate the vulnerability. Since the vulnerability requires local network access and is fixed in the stated version, applying the official update fully mitigates the risk.

Description

A vulnerability in the Airshare zeroconf Python library used by homeassistant-cli allows unauthenticated local network hosts to inject malformed mDNS records with invalid length fields. This causes cache corruption by desynchronizing the parser state and inserting attacker-shaped records into the local mDNS cache. The issue affects versions prior to 0.149.16 and is fixed in that version. It does not enable remote code execution or denial of service but can poison the local mDNS cache, potentially impacting services relying on zeroconf discovery.

Impact

The vulnerability enables local network attackers to corrupt the mDNS cache by injecting malformed records, which can lead to poisoning of the zeroconf discovery cache. This may impact the reliability and correctness of services that depend on zeroconf for local network service discovery. There is no direct impact on confidentiality or availability, and no remote code execution or denial of service is possible according to the provided data.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Oct 2026, 21:56 UTC

Technical details

References

Community reviews

Related threats