CVE-2026-64847: 
Python vulnerability analysis and mitigation

Overview

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

Technical details

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

Impact

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

Exploitability

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

Exploitation steps

  1. Identify target: Locate an application using 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().
  2. Craft malicious worker function: Write a Python function that writes a large volume of data (well exceeding 64 KiB, e.g., 1 MB) to sys.stderr before returning, such as:
import sys
def malicious_worker():
    sys.stderr.write('x' * (1024 * 1024))
    sys.stderr.flush()
    return 'done'
  1. Submit the function: Trigger the application to execute the crafted function via await anyio.to_process.run_sync(malicious_worker).
  2. Pipe buffer fills: The worker subprocess writes to its stderr pipe; since the parent never drains this pipe, the OS pipe buffer (typically 64 KiB) fills and the write() call in the worker blocks.
  3. Deadlock achieved: The worker never sends its stdout protocol response, causing the parent's run_sync() awaitable to hang indefinitely, denying service to any task waiting on that call (Github Advisory, Fix Commit).

Indicators of compromise

  • Process Behavior: Worker subprocesses spawned by the AnyIO process pool (child Python processes) that remain in a blocked/sleeping state indefinitely without returning, visible via ps aux or process monitoring tools showing persistent child Python processes.
  • Application Logs: Async tasks or coroutines awaiting to_process.run_sync() that never complete; application-level timeout errors or hung task warnings if timeouts are configured.
  • System Resources: Pipe file descriptors associated with worker subprocess stderr remaining open and full (observable via lsof or /proc/<pid>/fd); no abnormal network activity expected as this is a local attack vector.

Mitigation and workarounds

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.

Community reactions

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.

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

python-anyio

Affected

sid

python-anyio: 4.15.1-1

Fixed

trixie

python-anyio

Affected

Ubuntu

Affected

devel

python-anyio

Unknown

jammy

python-anyio

Affected

jammy (esm-apps)

python-anyio

Affected

noble

python-anyio

Affected

noble (esm-apps)

python-anyio

Affected

resolute

python-anyio

Affected

resolute (esm-apps)

python-anyio

Affected

RHEL / CentOS

Unknown

Source: This report was generated using AI

Related Python vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

GHSA-rh2h-69fp-q55vHIGH7
  • Python logoPython
  • virtualenv
NoYesNov 21, 2026
GHSA-vmhf-2rcw-c624MEDIUM4.5
  • Python logoPython
  • virtualenv
NoYesNov 21, 2026
GHSA-7c26-x6xg-6f39LOW3.6
  • Python logoPython
  • virtualenv
NoNoNov 21, 2026
GHSA-vg73-7844-8q8gLOW3.3
  • Python logoPython
  • virtualenv
NoYesNov 21, 2026
GHSA-rq56-gqmj-pggpLOW3.3
  • Python logoPython
  • virtualenv
NoYesNov 21, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management