medium CVSS 6.5 EPSS 0.24%

CVE-2026-47183·Python vulnerability

Zeroconf is a pure Python implementation of multicast DNS service discovery. Prior to 0.149.6, DNSIncoming._log_exception_debug and the four QuietLogger exception-dedup methods stored an unbounded _seen_logs dictionary keyed by attacker-influenced IncomingDecodeError messages, retaining sys.exc_info() tracebacks whose frame locals kept raw packet self.data buffers and allowing unauthenticated hosts on the local link over UDP/5353 (224.0.0.251 / ff02::fb) to drive memory growth until mDNS-dependent features degrade or the process is OOM-killed. This issue is fixed in version 0.149.6.

Severity
medium
Software
Python
Fixed in
0.149.6
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.24% — higher than 15% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Affected versions

Until: 0.149.6

Fixed in: 0.149.6

How to fix this CVE

Update the Python Zeroconf library to version 0.149.6 or later to fix a memory exhaustion vulnerability in the mDNS service discovery implementation. This vulnerability allows unauthenticated local network attackers to trigger unbounded memory growth by sending specially crafted multicast DNS packets, potentially causing application degradation or process termination. Affected systems running Zeroconf-dependent services should prioritize this update immediately.

sudo dnf update python3-zeroconf

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check the installed Zeroconf version with: pip3 show zeroconf | grep Version
  2. Step 2: Verify if mDNS services are active by checking for listening processes on port 5353: sudo netstat -tlnup | grep 5353 or sudo ss -tlnup | grep 5353
  3. Step 3: Monitor system memory usage during normal operation and look for unexplained growth patterns, especially if the system is on a shared local network: free -h && watch -n 1 free -h
  4. Step 4: After upgrading, re-run pip3 show zeroconf to confirm the version is 0.149.6 or higher

FAQ

What is CVE-2026-47183?

This vulnerability is a memory exhaustion flaw in Python Zeroconf's mDNS implementation where the library stores unbounded exception logs keyed by attacker-controlled error messages, allowing local network attackers to exhaust system memory and degrade or crash mDNS-dependent services.

Is CVE-2026-47183 being actively exploited?

No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available. However, it remains a valid denial-of-service concern for systems on untrusted local networks.

What versions of Python Zeroconf are affected by CVE-2026-47183?

All versions of python-zeroconf prior to 0.149.6 are vulnerable. The fix is included starting with version 0.149.6.

How do I check if my server is vulnerable to CVE-2026-47183?

Run pip3 show zeroconf and check the Version field. If the version is below 0.149.6, your system is vulnerable.

Does Defensia detect CVE-2026-47183?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Python Zeroconf is installed on a monitored server, CVE-2026-47183 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.
CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-26030CVSS 9.9Semantic Kernel, Microsoft's semantic kernel Python SDK, has a remote code execution vulnerability in versions prior to 1.39.4, specifically within the `InMemoryVectorStore` filter functionality. The problem has been fixed in version `python-1.39.4`. Users should upgrade this version or higher. As a workaround, avoid using `InMemoryVectorStore` for production scenarios.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-47183. Free for 1 server.

Get started free