Quick answers
- Is CVE-2026-54280 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54280 being exploited in the wild.
- How severe is CVE-2026-54280?
- Medium severity, with a CVSS score of 4, published 22 June 2026.
- Which products and versions are affected?
- aiohttp (PyPI) <= 3.14.0, ECOSYSTEM:introduced=0,fixed=3.14.1.
- Is there a fix for CVE-2026-54280?
- Yes. aiohttp (PyPI): upgrade to 3.14.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54280 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-54280?
- Check whether you run aiohttp (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- aiohttp (PyPI): upgrade to 3.14.1 or later
pip install "aiohttp>=3.14.1"
Technical details
AIOHTTP prior to version 3.14.1 contains a resource management vulnerability (CWE-404). When a remote client disconnects in the middle of a write operation, the framework fails to correctly close payload resources, such as open file handles. An attacker can exploit this by repeatedly initiating and then terminating connections during data transfer, leading to temporary resource starvation until the Python garbage collector eventually releases the handles. This issue is resolved in version 3.14.1.
Affected products
- aio-libs aiohttp < 3.14.1
Identifiers
- CVE-2026-54280
- GHSA-9x8q-7h8h-wcw9
- PYSEC-2026-2113
Timeline
- 2026-06-08: advisory: GitHub Security Advisory published
- 2026-06-22: disclosed: NVD publication date
- 2026-06-22: patched: Fix released in version 3.14.1