
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-64847 is a denial-of-service vulnerability in AnyIO, a high-level asynchronous concurrency and networking framework for Python, titled "AnyIO process-pool workers can block indefinitely on undrained stderr." It affects all versions of the anyio pip package prior to 4.14.2. The vulnerability was first published to the GitHub Advisory Database on July 7, 2026, and assigned a CVE on September 18, 2026. It carries a CVSS v3.1 base score of 5.5 (Medium) and a CVSS v4.0 base score of 6.8 (Medium) (Github Advisory, Feedly).
The root cause is classified under CWE-770 (Allocation of Resources Without Limits or Throttling) and CWE-1322 (Use of Blocking Code in Single-threaded, Non-blocking Context). AnyIO's to_process.run_sync() spawns process-pool worker subprocesses that redirect stdin and stdout to /dev/null to protect the inter-process protocol, but incorrectly leave stderr connected to a pipe that the parent process never drains — contradicting the documented behavior that all three standard streams are redirected. If worker code writes enough data to sys.stderr (e.g., more than the typical 64 KiB OS pipe buffer), the write blocks, preventing the worker from ever sending its stdout protocol response, which causes the awaiting run_sync() call in the parent to hang indefinitely. The fix, applied in commit f1b7301, adds a single line redirecting sys.stderr to os.devnull within the process_worker() function (Github Advisory, Fix Commit).
Successful exploitation results in a permanent availability impact: the affected to_process.run_sync() call blocks indefinitely, effectively deadlocking the async task that invoked it and potentially hanging the entire application or service relying on that process pool. There is no confidentiality or integrity impact. The scope is limited to applications that execute untrusted or faulty worker code capable of generating substantial stderr output, such as platforms that run user-supplied Python functions in process pools (Github Advisory).
No public proof-of-concept exploit code or in-the-wild exploitation has been reported. The NVD SSVC assessment confirms exploitation status as "none" and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The EPSS score is approximately 0.12–0.16%, placing it in the low percentile for near-term exploitation likelihood. Exploitation requires low privileges (local access to submit worker code) and is not automatable, limiting its practical attack surface to multi-tenant or plugin-based systems that execute user-controlled code via AnyIO process pools (Github Advisory, Feedly).
anyio versions < 4.14.2 that exposes a mechanism for a low-privileged user to submit callable code executed via anyio.to_process.run_sync().sys.stderr before returning, such as:import sys
def malicious_worker():
sys.stderr.write('x' * (1024 * 1024))
sys.stderr.flush()
return 'done'await anyio.to_process.run_sync(malicious_worker).write() call in the worker blocks.run_sync() awaitable to hang indefinitely, denying service to any task waiting on that call (Github Advisory, Fix Commit).ps aux or process monitoring tools showing persistent child Python processes.to_process.run_sync() that never complete; application-level timeout errors or hung task warnings if timeouts are configured.lsof or /proc/<pid>/fd); no abnormal network activity expected as this is a local attack vector.Upgrade anyio to version 4.14.2 or later, which redirects sys.stderr to os.devnull in worker processes, matching the documented behavior and eliminating the deadlock condition (AnyIO Release). As a temporary workaround for applications that cannot immediately upgrade, closing or redirecting sys.stderr at the start of each target function passed to run_sync() will prevent the deadlock (Github Advisory). Red Hat has also issued errata (RHSA-2026:70965, RHSA-2026:70979, RHSA-2026:70995, RHSA-2026:70996, RHSA-2026:73929) for affected Red Hat products, and SUSE has published SUSE-SU-2026:4416-1.
The vulnerability was disclosed by the AnyIO project maintainer (agronholm) directly via a GitHub Security Advisory, with the fix merged promptly on July 8, 2026 (Fix PR). Downstream projects such as headroomlabs-ai/headroom and rafaelpierre/superset have opened dependency update issues referencing this CVE. Red Hat and SUSE both issued security advisories and errata, indicating broad ecosystem awareness. No significant independent researcher commentary or media coverage beyond standard vulnerability tracking has been identified.
Fix availability across major Linux distributions and their releases.
devel
python-anyio
jammy
python-anyio
jammy (esm-apps)
python-anyio
noble
python-anyio
noble (esm-apps)
python-anyio
resolute
python-anyio
resolute (esm-apps)
python-anyio
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."