CVE-2026-47180

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 94% 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: cna:github_m, epss
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

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

zeroconf has unbounded recursion in DNS compression-pointer decoder that allows LAN-local denial of service

Impact

DNSIncoming._decode_labels_at_offset recurses once per DNS-name compression pointer (RFC 1035 §4.1.4). Pointer cycles and label counts were capped, but the chain length of unique forward pointers was not. A single ~3 kB mDNS packet carrying ~1500 chained pointers drives the recursion past CPython's default limit, and RecursionError was not listed in DECODE_EXCEPTIONS, so it escaped DNSIncoming.__init__ and was logged by asyncio's default exception handler.

Any unauthenticated host on the local link (UDP/5353, 224.0.0.251 / ff02::fb) can degrade the mDNS listener; that includes a guest on the same Wi-Fi, a compromised IoT device, or a container on a shared bridge. Replaying at a few hertz produces sustained CPU burn and log flooding, and mDNS-dependent features (HomeKit, Chromecast/Matter, AirPlay, printers) degrade while the attack is in flight.

Patches

Fixed in zeroconf 0.149.5 (PR #1719). Upgrade to >= 0.149.5.

Workarounds

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

Resources

CVSS v3
6.5
EG Score
6.5(low)
EPSS
5.7%
KEV
Not listed

Published

May 29, 2026

Last Modified

May 29, 2026

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

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
zeroconf0.100.0 ... 0.99.0 (251 versions)0.149.5

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-47180?
CVE-2026-47180 is a medium vulnerability published on May 29, 2026. zeroconf has unbounded recursion in DNS compression-pointer decoder that allows LAN-local denial of service Impact DNSIncoming.decodelabelsatoffset recurses once per DNS-name compression pointer (RFC 1035 §4.1.4). Pointer cycles and label counts were capped, but the chain length of unique forward…
When was CVE-2026-47180 disclosed?
CVE-2026-47180 was first published in the National Vulnerability Database on May 29, 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 5.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47180?
CVE-2026-47180 has a CVSS v4.0 base score of 6.5 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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.