Debian Package Tracker
Register | Log in
Subscribe

python-anyio

Asynchronous compatibility layer

Choose email to subscribe with

general
  • source: python-anyio (main)
  • version: 4.15.1-1
  • maintainer: Debian Python Team (DMD)
  • uploaders: Julien Puydt [DMD]
  • arch: all
  • std-ver: 4.7.4
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 2.0.2-2
  • oldstable: 3.6.2-1
  • stable: 4.8.0-3
  • testing: 4.12.1-3
  • unstable: 4.15.1-1
versioned links
  • 2.0.2-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.6.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 4.8.0-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 4.12.1-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 4.15.1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • python3-anyio
action needed
Marked for autoremoval on 29 October due to sphinxcontrib-log-cabinet: #1147863 high
Version 4.12.1-3 of python-anyio is marked for autoremoval from testing on Thu 29 Oct 2026. It depends (transitively) on sphinxcontrib-log-cabinet, affected by #1147863. You should try to prevent the removal by fixing these RC bugs.
Created: 2026-09-22 Last update: 2026-09-23 23:03
3 security issues in trixie high

There are 3 open security issues in trixie.

3 important issues:
  • CVE-2026-63349: AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. In 4.14.0, AnyIO accepts the POSIX extra_groups argument in anyio.run_process() and anyio.open_process(), but open_process() forwards the group argument to the backend instead of extra_groups. A caller that supplies extra_groups=[] to clear inherited supplementary groups can therefore launch a child that retains the parent process groups, undermining a privilege-dropping boundary. If group is also supplied, the integer group value is passed where an iterable of supplementary groups is expected and the launch can fail with TypeError. This issue affects POSIX applications that rely on AnyIO subprocess helpers to launch less-privileged child processes. This issue is fixed in version 4.14.2.
  • CVE-2026-63374: AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. Prior to 4.14.2, connect_tcp() and TLSStream.wrap() can validate internationalized host names after the standard library converts them with IDNA 2003 instead of IDNA 2008. When a connection to a non-ASCII domain is hijacked or redirected, an attacker can obtain a legitimate certificate for the different ASCII hostname produced by IDNA 2003 and present it to the client, causing the malicious endpoint's certificate to validate. This issue is fixed in version 4.14.2.
  • CVE-2026-64847: AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. Prior to 4.14.2, AnyIO starts process-pool workers with standard error connected to a pipe that the parent never drains, even though the documented behavior redirects all three standard streams. Worker code that writes enough attacker-influenced data to sys.stderr can fill the pipe and block before returning the standard-output protocol response, causing the awaiting process-pool call to remain blocked indefinitely. Applications that run untrusted or faulty worker code capable of producing substantial standard-error output are affected. This issue is fixed in version 4.14.2.
Created: 2026-09-20 Last update: 2026-09-23 18:00
3 security issues in forky high

There are 3 open security issues in forky.

3 important issues:
  • CVE-2026-63349: AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. In 4.14.0, AnyIO accepts the POSIX extra_groups argument in anyio.run_process() and anyio.open_process(), but open_process() forwards the group argument to the backend instead of extra_groups. A caller that supplies extra_groups=[] to clear inherited supplementary groups can therefore launch a child that retains the parent process groups, undermining a privilege-dropping boundary. If group is also supplied, the integer group value is passed where an iterable of supplementary groups is expected and the launch can fail with TypeError. This issue affects POSIX applications that rely on AnyIO subprocess helpers to launch less-privileged child processes. This issue is fixed in version 4.14.2.
  • CVE-2026-63374: AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. Prior to 4.14.2, connect_tcp() and TLSStream.wrap() can validate internationalized host names after the standard library converts them with IDNA 2003 instead of IDNA 2008. When a connection to a non-ASCII domain is hijacked or redirected, an attacker can obtain a legitimate certificate for the different ASCII hostname produced by IDNA 2003 and present it to the client, causing the malicious endpoint's certificate to validate. This issue is fixed in version 4.14.2.
  • CVE-2026-64847: AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. Prior to 4.14.2, AnyIO starts process-pool workers with standard error connected to a pipe that the parent never drains, even though the documented behavior redirects all three standard streams. Worker code that writes enough attacker-influenced data to sys.stderr can fill the pipe and block before returning the standard-output protocol response, causing the awaiting process-pool call to remain blocked indefinitely. Applications that run untrusted or faulty worker code capable of producing substantial standard-error output are affected. This issue is fixed in version 4.14.2.
Created: 2026-09-20 Last update: 2026-09-23 18:00
3 security issues in bookworm high

There are 3 open security issues in bookworm.

3 important issues:
  • CVE-2026-63349: AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. In 4.14.0, AnyIO accepts the POSIX extra_groups argument in anyio.run_process() and anyio.open_process(), but open_process() forwards the group argument to the backend instead of extra_groups. A caller that supplies extra_groups=[] to clear inherited supplementary groups can therefore launch a child that retains the parent process groups, undermining a privilege-dropping boundary. If group is also supplied, the integer group value is passed where an iterable of supplementary groups is expected and the launch can fail with TypeError. This issue affects POSIX applications that rely on AnyIO subprocess helpers to launch less-privileged child processes. This issue is fixed in version 4.14.2.
  • CVE-2026-63374: AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. Prior to 4.14.2, connect_tcp() and TLSStream.wrap() can validate internationalized host names after the standard library converts them with IDNA 2003 instead of IDNA 2008. When a connection to a non-ASCII domain is hijacked or redirected, an attacker can obtain a legitimate certificate for the different ASCII hostname produced by IDNA 2003 and present it to the client, causing the malicious endpoint's certificate to validate. This issue is fixed in version 4.14.2.
  • CVE-2026-64847: AnyIO is a high level asynchronous concurrency and networking framework that works on top of either Trio or asyncio. Prior to 4.14.2, AnyIO starts process-pool workers with standard error connected to a pipe that the parent never drains, even though the documented behavior redirects all three standard streams. Worker code that writes enough attacker-influenced data to sys.stderr can fill the pipe and block before returning the standard-output protocol response, causing the awaiting process-pool call to remain blocked indefinitely. Applications that run untrusted or faulty worker code capable of producing substantial standard-error output are affected. This issue is fixed in version 4.14.2.
Created: 2026-09-20 Last update: 2026-09-23 18:00
testing migrations
  • excuses:
    • Migration status for python-anyio (4.12.1-3 to 4.15.1-1): BLOCKED: Rejected/violates migration policy/introduces a regression
    • Issues preventing migration:
    • ∙ ∙ Autopkgtest for aiocomelit/3.0.0-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for aiohttp-socks/0.11.0-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for asgi-lifespan/2.1.0-4: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for hishel/1.1.9-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for httpcore/1.0.9-1.1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for httpx/0.28.1-1.1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Regression ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for jupyter-server/2.20.0-3: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for ormar/0.24.0-2: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for psycopg3/3.3.5-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for pyatmo/9.9.1-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for pytest-subprocess/1.6.0-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-aiobotocore/2.25.2-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-aiooncue/0.3.7-2: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-anyio/4.15.1-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Regression ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for python-asyncclick/8.3.0.5+async-3: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-asyncio-mqtt/2.3.1-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-authlib/1.7.2-2: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-elastic-transport/9.4.2-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-elasticsearch/9.5.1-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-gardena-bluetooth/1.4.3-1.1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-gql/4.3.0b3-2: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Failed (not a regression) ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for python-httpx2/2.12.0-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-openai/3.6.0-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-respx/0.22.0-3: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-returns/0.29.0-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for python-socks/2.8.1-2: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-sse-starlette/3.4.11-2: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-stamina/26.1.0+dfsg-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-tiny-proxy/0.2.1-1: amd64: No tests, superficial or marked flaky ♻, arm64: Test triggered, armhf: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for python-uvicorn/0.38.0-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for python-watchfiles/1.2.0-1: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for qtile/0.36.0-1: amd64: No tests, superficial or marked flaky ♻, arm64: Test triggered, armhf: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for sphinx-needs/5.1.0+dfsg-8: amd64: Pass, arm64: Test triggered, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
    • ∙ ∙ Autopkgtest for starlette/1.6.0-1: amd64: Regression ♻ (reference ♻), arm64: Test triggered, armhf: Regression ♻ (reference ♻), i386: Test triggered, ppc64el: Regression ♻ (reference ♻), riscv64: Regression ♻ (reference ♻)
    • ∙ ∙ Too young, only 1 of 5 days old
    • Additional info (not blocking):
    • ∙ ∙ Updating python-anyio will fix bugs in testing: #1148561
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-anyio.html
    • ∙ ∙ Reproduced on amd64 - info
    • ∙ ∙ Reproduced on arm64 - info
    • ∙ ∙ Reproduced on armhf - info
    • ∙ ∙ Reproduced on i386 - info
    • Not considered
news
[rss feed]
  • [2026-09-23] Accepted python-anyio 4.15.1-1 (source) into unstable (Colin Watson)
  • [2026-06-30] python-anyio 4.12.1-3 MIGRATED to testing (Debian testing watch)
  • [2026-06-25] Accepted python-anyio 4.12.1-3 (source) into unstable (Alexandre Detiste)
  • [2026-06-20] python-anyio 4.12.1-2 MIGRATED to testing (Debian testing watch)
  • [2026-06-17] Accepted python-anyio 4.12.1-2 (source) into unstable (Edward Betts)
  • [2026-03-03] python-anyio 4.12.1-1 MIGRATED to testing (Debian testing watch)
  • [2026-02-25] Accepted python-anyio 4.12.1-1 (source) into unstable (Alexandre Detiste)
  • [2025-10-31] python-anyio 4.11.0-3 MIGRATED to testing (Debian testing watch)
  • [2025-10-29] Accepted python-anyio 4.11.0-3 (source) into unstable (Colin Watson)
  • [2025-10-02] python-anyio 4.11.0-2 MIGRATED to testing (Debian testing watch)
  • [2025-09-29] Accepted python-anyio 4.11.0-2 (source) into unstable (Andrey Rakhmatullin) (signed by: Andrey Rahmatullin)
  • [2025-09-28] Accepted python-anyio 4.11.0-1 (source) into unstable (Andrey Rakhmatullin) (signed by: Andrey Rahmatullin)
  • [2025-03-19] python-anyio 4.8.0-3 MIGRATED to testing (Debian testing watch)
  • [2025-03-16] Accepted python-anyio 4.8.0-3 (source) into unstable (Colin Watson)
  • [2025-03-09] Accepted python-anyio 4.8.0-2 (source) into unstable (Colin Watson)
  • [2025-01-27] Accepted python-anyio 4.8.0-1 (source) into unstable (Julien Puydt)
  • [2025-01-10] python-anyio 4.7.0-1 MIGRATED to testing (Debian testing watch)
  • [2025-01-04] Accepted python-anyio 4.7.0-1 (source) into unstable (Julien Puydt)
  • [2024-11-15] python-anyio 4.6.2-4 MIGRATED to testing (Debian testing watch)
  • [2024-11-12] Accepted python-anyio 4.6.2-4 (source) into unstable (Julian Gilbey)
  • [2024-11-12] Accepted python-anyio 4.6.2-3 (source) into unstable (Julian Gilbey)
  • [2024-11-11] Accepted python-anyio 4.6.2-2 (source) into unstable (Julian Gilbey)
  • [2024-11-10] Accepted python-anyio 4.6.2-1 (source) into unstable (Julian Gilbey)
  • [2024-09-26] Accepted python-anyio 4.6.0-1 (source) into unstable (Julien Puydt)
  • [2024-08-17] python-anyio 4.4.0-1 MIGRATED to testing (Debian testing watch)
  • [2024-06-09] Accepted python-anyio 4.4.0-1 (source) into unstable (Julien Puydt)
  • [2024-04-04] python-anyio 4.3.0-1 MIGRATED to testing (Debian testing watch)
  • [2024-04-01] Accepted python-anyio 4.3.0-1 (source) into unstable (Julien Puydt)
  • [2024-02-10] python-anyio 4.2.0-1 MIGRATED to testing (Debian testing watch)
  • [2024-01-18] Accepted python-anyio 4.2.0-1 (source) into unstable (Julien Puydt)
  • 1
  • 2
bugs [bug history graph]
  • all: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • other distros
  • security tracker
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 4.12.1-3

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing