CVE-2026-48487

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Zeroconf is a pure Python implementation of multicast DNS service discovery. Prior to 0.149.16, _read_character_string and _read_string in src/zeroconf/_protocol/incoming.py advanced self.offset by attacker-declared RDLENGTH without checking it against self._data_len, allowing unauthenticated hosts on the local link over UDP/5353 (224.0.0.251 / ff02::fb) to send a TXT, HINFO, or A/AAAA record with rdlength=65535 and seed DNSCache and ServiceInfo.properties with truncated, attacker-shaped key/value or address records. This issue is fixed in version 0.149.16.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

June 22, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Jul 17, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Unvalidated rdlength in record payload readers allows LAN-local cache corruption via crafted mDNS packet · Advisory · python-zeroconf/python-zeroconf · GitHub

https://github.com/python-zeroconf/python-zeroconf/security/advisories/GHSA-qc2x-6f54-m6h9
github_release Patch Available

0.149.16

Patch available: python-zeroconf/python-zeroconf 0.149.16

https://github.com/python-zeroconf/python-zeroconf/releases/tag/0.149.16
github_pr Patch Available

fix: bound record payload reads against rdlength overrun

Patch available: python-zeroconf/python-zeroconf 0.149.13 (PR #1756 merged 2026-05-20)

https://github.com/python-zeroconf/python-zeroconf/pull/1756
generic

Security: `_read_string`/`_read_character_string` skip remaining-byte validation, enabling silent record-data corruption · Issue #1752 · python-zeroconf/python-zeroconf · GitHub

https://github.com/python-zeroconf/python-zeroconf/issues/1752
github_commit Patch Available

commit 544449596e64 (python-zeroconf/python-zeroconf)

Patch available: python-zeroconf/python-zeroconf 0.149.13 (contains commit 544449596e64)

https://github.com/python-zeroconf/python-zeroconf/commit/544449596e645fcaad3834fa0cb614a54f847a82

Vendor Advisories for CVE-2026-48487(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-zeroconf0.102.0-1 ... 0.97.0-1 (111 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-zeroconf0.102.0-1 ... 0.97.0-1 (79 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-zeroconf0.147.0-1 ... 0.150.0-1 (13 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-zeroconf0.147.0-1 ... 0.149.9-1 (11 versions)0.149.16-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
zeroconf0.100.0 ... 0.99.0 (259 versions)0.149.16—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 52× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-23 14:18 UTCEG score recompute
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-22 14:54 UTCEG score recompute
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-21 07:20 UTCEG score recompute
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 07:49 UTCEG score recompute
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 04:51 UTCEG score recompute
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 20:11 UTCEG score recompute
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 20:17 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 20:52 UTCEG score recompute
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 21:04 UTCEG score recompute
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-12 21:53 UTCEG score recompute
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-11 22:28 UTCEG score recompute
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 23:39 UTCEG score recompute
  25. 2026-08-09 13:46 UTCEPSS rescore
Show 37 more
  1. 2026-08-09 00:15 UTCEG score recompute
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-08 00:50 UTCEG score recompute
  4. 2026-08-07 01:26 UTCEG score recompute
  5. 2026-08-06 13:47 UTCEPSS rescore
  6. 2026-08-06 02:01 UTCEG score recompute
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-05 02:36 UTCEG score recompute
  9. 2026-08-04 15:10 UTCEPSS rescore
  10. 2026-08-04 10:39 UTCEPSS rescore
  11. 2026-08-04 02:51 UTCEG score recompute
  12. 2026-08-03 10:36 UTCEPSS rescore
  13. 2026-08-02 03:51 UTCEG score recompute
  14. 2026-08-02 02:27 UTCEPSS rescore
  15. 2026-08-01 04:26 UTCEG score recompute
  16. 2026-08-01 04:16 UTCEPSS rescore
  17. 2026-07-31 04:16 UTCEG score recompute
  18. 2026-07-30 16:28 UTCEPSS rescore
  19. 2026-07-30 04:50 UTCEG score recompute
  20. 2026-07-30 01:30 UTCEPSS rescore
  21. 2026-07-29 05:23 UTCEG score recompute
  22. 2026-07-28 15:37 UTCEPSS rescore
  23. 2026-07-28 05:54 UTCEG score recompute
  24. 2026-07-27 06:28 UTCEG score recompute
  25. 2026-07-26 14:54 UTCEPSS rescore
  26. 2026-07-26 05:13 UTCEG score recompute
  27. 2026-07-25 14:18 UTCEPSS rescore
  28. 2026-07-24 14:18 UTCEPSS rescore
  29. 2026-07-23 14:18 UTCEPSS rescore
  30. 2026-07-23 03:18 UTCEG score recompute▼ 1.20
  31. 2026-07-22 14:08 UTCEPSS rescore
  32. 2026-07-21 15:25 UTCEPSS rescore
  33. 2026-07-20 17:08 UTCEPSS rescore
  34. 2026-07-19 14:31 UTCEPSS rescore
  35. 2026-07-19 02:29 UTCEPSS rescore
  36. 2026-07-17 18:34 UTCMITRE cvelistV5CVSS v3 → 5.3 · CVSS v4 → 5.3
  37. 2026-06-22 23:31 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48487?
CVE-2026-48487 is a medium vulnerability published on June 22, 2026. Zeroconf is a pure Python implementation of multicast DNS service discovery. Prior to 0.149.16, readcharacterstring and readstring in src/zeroconf/protocol/incoming.py advanced self.offset by attacker-declared RDLENGTH without checking it against self.datalen, allowing unauthenticated hosts on the…
When was CVE-2026-48487 disclosed?
CVE-2026-48487 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48487 actively exploited?
CVE-2026-48487 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.6% of all scored CVEs.
What is the CVSS score of CVE-2026-48487?
CVE-2026-48487 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-48487?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48487, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48487

Explore →

Is Your Infrastructure Affected by CVE-2026-48487?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs