Vulnerabilities in pkg:pypi/zeroconf
PACKAGECVE-2026-48487 is a MODERATE (CVSS 6.5) unvalidated rdlength vulnerability (CWE-130: Improper Handling of Length Parameter Inconsistency) affecting zeroconf libraries in the PyPI ecosystem. The issue involves unvalidated rdlength in record payload readers allows lan-local cache corruption via crafted mdns packet. Remediation is available by upgrading affected packages to version 0.149.16.
pkg:pypi/zeroconf
Vulnerability advisories affecting package pkg:pypi/zeroconf. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-qc2x-6f54-m6h9 | CVE-2026-48487 | MODERATE | zeroconf: Unvalidated rdlength in record payload readers allows LAN-local cache corruption via crafted mDNS packet |
| GHSA-9663-mqmp-p9mm | CVE-2026-48045 | MODERATE | python-zeroconf: Unbounded TC-deferred queue allows LAN-local memory exhaustion via spoofed-source flood |
| GHSA-rfg2-pjw2-56x2 | CVE-2026-47184 | MODERATE | zeroconf has unbounded DNS record cache that allows LAN-local memory exhaustion via multicast flood |
| GHSA-phvx-9mgw-67r5 | CVE-2026-47183 | MODERATE | zeroconf: Unbounded exception-dedup state retains packet buffers via traceback frame locals, enabling LAN-local memory exhaustion |
| GHSA-9pgc-3ccv-5297 | CVE-2026-47180 | MODERATE | zeroconf has unbounded recursion in DNS compression-pointer decoder that allows LAN-local denial of service |
CVE-2026-48487 at a Glance
Security Impact
CVSS: 6.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).
How to Fix CVE-2026-48487
To remediate this vulnerability, upgrade all affected zeroconf dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
pip install zeroconf>=0.149.16
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
pip show zeroconf
How to Check if You Are Affected
To determine whether your Python environment is affected by CVE-2026-48487, inspect your installed packages using pip:
pip show zeroconf
Analyze the terminal output to locate any version of zeroconf in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.149.16), your application is affected.
Note: The pip show zeroconf command checks currently installed packages in your active Python environment.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-130: Improper Handling of Length Parameter Inconsistency, where the product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data. In zeroconf, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-48487 Affected zeroconf Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
zeroconf
|
PyPI |
< 0.149.16
|
0.149.16
|
References
Frequently Asked Questions
What is CVE-2026-48487?
Which zeroconf versions are affected?
What version fixes CVE-2026-48487?
Is zeroconf affected?
What is the CVSS score of CVE-2026-48487?
What CWE is associated with CVE-2026-48487?
How can I check PyPI dependencies for CVE-2026-48487?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-qc2x-6f54-m6h9",
"modified" : "2026-06-22T23:07:44Z",
"published" : "2026-06-22T23:07:44Z",
"aliases" : [ "CVE-2026-48487" ],
"summary" : "zeroconf: Unvalidated rdlength in record payload readers allows LAN-local cache corruption via crafted mDNS packet",
"details" : "### Impact\n\n`_read_character_string` and `_read_string` in `src/zeroconf/_protocol/incoming.py` sliced `self.data[self.offset : self.offset + length]` and advanced `self.offset` by the declared `length` without checking it against `self._data_len`. Python's slice silently returns fewer bytes when the end index runs past the buffer, so a record whose 16-bit RDLENGTH (RFC 1035 §3.2.1) over-advertised by tens of kilobytes was constructed from a truncated payload, appended to `DNSIncoming._answers`, and committed to the cache before any later parse failure surfaced. The follow-up `_read_name` for the next record then failed, but the corrupt record had already entered the answer list and propagated to `DNSCache` and `ServiceInfo`.\n\nAny unauthenticated host on the local link (UDP/5353, `224.0.0.251` / `ff02::fb`) can multicast a single mDNS response carrying a TXT, HINFO, or A/AAAA record that advertises rdlength=65535 and only a handful of real payload bytes; consumers calling `ServiceInfo.properties` then parse the truncated bytes as if they matched the wire, and downstream integrations (Home Assistant and other zeroconf-driven discovery) trust the decoded record. The bug is parser-state desync rather than RCE, but it seeds the cache with attacker-shaped key/value and address records for a TTL window and is a building block for higher-impact chains.\n\nThe impact is likely lower than the other recently released advisories as there is no additional risk of OOM so the severity was manually set to low to override the score CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N (6.5, Medium) since that doesn't fully consider the mDNS threat model.\n\n### Patches\n\nFixed in `zeroconf` 0.149.16 ([PR #1756](https://github.com/python-zeroconf/python-zeroconf/pull/1756)). Note that this change originally intended to ship in 0.149.13 but we ran out of space on PyPI: see https://github.com/python-zeroconf/python-zeroconf/issues/1769\n\nUpgrade to `>= 0.149.16`.\n\n### Workarounds\n\nThere is no in-process workaround; upgrading is the fix. Otherwise, restrict mDNS (UDP/5353) to trusted Layer-2 segments via AP client isolation, guest-network separation, or host firewall rules.\n\n### Resources\n\n- [PR #1756](https://github.com/python-zeroconf/python-zeroconf/pull/1756), fix\n- [Issue #1752](https://github.com/python-zeroconf/python-zeroconf/issues/1752), public tracking issue\n- [RFC 1035 §3.2.1](https://www.rfc-editor.org/rfc/rfc1035#section-3.2.1), [RFC 1035 §3.3](https://www.rfc-editor.org/rfc/rfc1035#section-3.3), [CWE-130](https://cwe.mitre.org/data/definitions/130.html)",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "PyPI",
"name" : "zeroconf"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.149.16"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/python-zeroconf/python-zeroconf/security/advisories/GHSA-qc2x-6f54-m6h9"
}, {
"type" : "WEB",
"url" : "https://github.com/python-zeroconf/python-zeroconf/issues/1752"
}, {
"type" : "WEB",
"url" : "https://github.com/python-zeroconf/python-zeroconf/pull/1756"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/python-zeroconf/python-zeroconf"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-130" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-06-22T23:07:44Z",
"nvd_published_at" : null
}
}