CVE-2026-64847: AnyIO process-pool workers can block indefinitely on undrained stderr
Impact AnyIO starts process-pool workers with stderr connected to a pipe but never drains that pipe. The worker redirects stdin and stdout to /dev/null to protect its protocol, but does not redirect stderr even though the documentation says all three standard streams are redirected.
Published Sep 18, 2026
Affected packages
anyio
- Ecosystem
- PyPI
- Affected
- < 4.14.2
- Fixed in
- 4.14.2
- Check
pip show anyio
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
AnyIO starts process-pool workers with stderr connected to a pipe but never drains that pipe. The worker redirects stdin and stdout to /dev/null to protect its protocol, but does not redirect stderr even though the documentation says all three standard streams are redirected. Worker code that writes enough attacker-influenced data to stderr can fill the pipe, block before returning the stdout protocol response, and wedge the awaiting process-pool call.
Anyone who runs untrusted or faulty code that writes too much to stderr is at risk.
Patches
This vulnerability will be patched in v4.14.2.
Workarounds
Closing sys.stderr in the target function should at least prevent the deadlock.
References
- https://github.com/agronholm/anyio/security/advisories/GHSA-5p39-cfhj-2xmp
- https://github.com/agronholm/anyio/pull/1207
- https://github.com/agronholm/anyio/commit/f1b7301c8264b0d2e8d24a5788fd29e93dea4040
- https://github.com/agronholm/anyio/releases/tag/4.14.2
- https://github.com/advisories/GHSA-5p39-cfhj-2xmp
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
