CVE-2026-47180

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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, secondary
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: 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.5, DNSIncoming._decode_labels_at_offset recurses once per DNS-name compression pointer, and a single mDNS packet carrying chained pointers can trigger a RecursionError that escapes DNSIncoming.__init__, causing sustained CPU burn, log flooding, and degraded mDNS-dependent features for unauthenticated hosts on the local link over UDP/5353 (224.0.0.251 / ff02::fb). This issue is fixed in version 0.149.5.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

May 29, 2026

Last Modified

August 17, 2026

Advisory Details (4)

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

0.149.5

Patch available: python-zeroconf/python-zeroconf 0.149.5

https://github.com/python-zeroconf/python-zeroconf/releases/tag/0.149.5
github_commit Patch Available

commit f9e23592137f (python-zeroconf/python-zeroconf)

Patch available: python-zeroconf/python-zeroconf 0.149.5 (contains commit f9e23592137f)

https://github.com/python-zeroconf/python-zeroconf/commit/f9e23592137f30fdf7ef710dba065da31c79b1cf
github_pr Patch Available

fix: bound DNS compression-pointer chain depth in DNSIncoming

Patch available: python-zeroconf/python-zeroconf 0.149.5 (PR #1719 merged 2026-05-18)

https://github.com/python-zeroconf/python-zeroconf/pull/1719
github Patch Available

Unbounded recursion in DNS compression-pointer decoder allows LAN-local denial of service · Advisory · python-zeroconf/python-zeroconf · GitHub

https://github.com/python-zeroconf/python-zeroconf/security/advisories/GHSA-9pgc-3ccv-5297

Vendor Advisories for CVE-2026-47180(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.148.0-4 (8 versions)0.149.6-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
zeroconf0.100.0 ... 0.99.0 (251 versions)0.149.5—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 40× 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-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 04:15 UTCEG score recompute
  11. 2026-08-23 14:10 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 14:59 UTCEG score recompute
  15. 2026-08-20 22:55 UTCEPSS rescore
  16. 2026-08-20 10:24 UTCEG score recompute
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 19:49 UTCEG score recompute
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 06:51 UTCEG score recompute
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 03:09 UTCEG score recompute
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 02:49 UTCEG score recompute
Show 47 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 02:21 UTCEG score recompute
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 02:00 UTCEG score recompute
  5. 2026-08-12 13:51 UTCEPSS rescore
  6. 2026-08-12 01:40 UTCEG score recompute
  7. 2026-08-11 01:19 UTCEG score recompute
  8. 2026-08-11 00:00 UTCEPSS rescore
  9. 2026-08-10 00:59 UTCEG score recompute
  10. 2026-08-09 13:46 UTCEPSS rescore
  11. 2026-08-09 00:38 UTCEG score recompute
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-08 00:17 UTCEG score recompute
  14. 2026-08-06 23:57 UTCEG score recompute
  15. 2026-08-06 13:47 UTCEPSS rescore
  16. 2026-08-05 23:23 UTCEG score recompute
  17. 2026-08-05 19:17 UTCEPSS rescore
  18. 2026-08-04 23:02 UTCEG score recompute
  19. 2026-08-04 15:10 UTCEPSS rescore
  20. 2026-08-04 10:39 UTCEPSS rescore
  21. 2026-08-03 15:55 UTCEG score recompute
  22. 2026-08-03 10:36 UTCEPSS rescore
  23. 2026-08-02 14:16 UTCEG score recompute
  24. 2026-08-02 02:27 UTCEPSS rescore
  25. 2026-08-01 13:55 UTCEG score recompute
  26. 2026-08-01 04:16 UTCEPSS rescore
  27. 2026-07-31 05:51 UTCEG score recompute
  28. 2026-07-30 16:28 UTCEPSS rescore
  29. 2026-07-30 01:30 UTCEPSS rescore
  30. 2026-07-29 11:47 UTCEG score recompute
  31. 2026-07-28 15:37 UTCEPSS rescore
  32. 2026-07-27 09:02 UTCEG score recompute
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-26 07:37 UTCEG score recompute
  35. 2026-07-25 14:18 UTCEPSS rescore
  36. 2026-07-24 14:17 UTCEPSS rescore
  37. 2026-07-23 14:18 UTCEPSS rescore
  38. 2026-07-23 03:17 UTCEG score recompute
  39. 2026-07-22 14:08 UTCEPSS rescore
  40. 2026-07-21 15:24 UTCEPSS rescore
  41. 2026-07-20 17:08 UTCEPSS rescore
  42. 2026-07-19 14:31 UTCEPSS rescore
  43. 2026-07-19 02:29 UTCEPSS rescore
  44. 2026-06-14 23:18 UTCEPSS rescore
  45. 2026-06-13 23:00 UTCEPSS rescore
  46. 2026-06-12 23:12 UTCEPSS rescore
  47. 2026-05-29 20:20 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47180?
CVE-2026-47180 is a medium vulnerability published on May 29, 2026. Zeroconf is a pure Python implementation of multicast DNS service discovery. Prior to 0.149.5, DNSIncoming.decodelabelsatoffset recurses once per DNS-name compression pointer, and a single mDNS packet carrying chained pointers can trigger a RecursionError that escapes DNSIncoming.init, causing…
When was CVE-2026-47180 disclosed?
CVE-2026-47180 was first published in the National Vulnerability Database on May 29, 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-47180 actively exploited?
CVE-2026-47180 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 69.9% of all scored CVEs.
What is the CVSS score of CVE-2026-47180?
CVE-2026-47180 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-47180?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47180, 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-47180

Explore →

Is Your Infrastructure Affected by CVE-2026-47180?

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

Start Free Scan →Browse All CVEs