Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-54280

aiohttp: AIOHTTP: Denial of Service due to improper resource handling

Overview

Published
22 Jun 2026
Modified
25 Oct 2026
Low CVE
3 Registry packages
38 OS packages
7 Linux distributions
Yes Fix available

Description

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, payload resources are not closed correctly when a client disconnects in the middle of a write. If a payload is using an open file or similar limited resource, then an attacker may be able to cause resource starvation temporarily until garbage collection or similar closes the file. This vulnerability is fixed in 3.14.1.

Source: OX vulnerability database

Severity

7.5 · LOW

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Weakness: CWE-404

Affected packages · 3

Packages affected by CVE-2026-54280
EcosystemPackageVulnerableFixed in
PyPI aiohttp <3.14.1 3.14.1
Seal PyPI aiohttp >=2.3.9+sp0, <2.3.9+sp999>=3.0.8+sp0, <3.0.8+sp999>=3.11.18+sp0, <3.11.18+sp999>=3.12.9+sp0, <3.12.9+sp2>=3.13.2+sp0, <3.13.2+sp999+4 more 2.3.9+sp9993.0.8+sp9993.11.18+sp9993.12.9+sp23.13.2+sp999
Seal PyPI seal-aiohttp >=2.3.9+sp1, <2.3.9+sp999>=3.0.8+sp1, <3.0.8+sp999>=3.11.18+sp1, <3.11.18+sp999>=3.12.9+sp1, <3.12.9+sp2>=3.13.2+sp1, <3.13.2+sp999+4 more 2.3.9+sp9993.0.8+sp9993.11.18+sp9993.12.9+sp23.13.2+sp999

Open a package to see all its vulnerabilities.

Operating systems · 50 fixes

SUSE Linux Enterprise 5 releases · 3 packages

fixed 9
python3-aiohttp python311-aiohttp python313-aiohttp
SUSE Linux Enterprise fixes for CVE-2026-54280
ReleasePackageFixed inAdvisory
15.4 python3-aiohttp 3.6.0-150100.3.38.1 SUSE-SU-2026:3208-1
15.4 python311-aiohttp 3.9.3-150400.10.43.1 SUSE-SU-2026:3207-1
15.5 python3-aiohttp 3.6.0-150100.3.38.1 SUSE-SU-2026:3208-1
15.5 python311-aiohttp 3.9.3-150400.10.43.1 SUSE-SU-2026:3207-1
15.6 python3-aiohttp 3.6.0-150100.3.38.1 SUSE-SU-2026:3208-1
15.6 python311-aiohttp 3.9.3-150400.10.43.1 SUSE-SU-2026:3207-1

3 more rows

chainguard 1 release · 23 packages

fixed 23
py3-13-scanner-test-libraries-aiohttp py3-vllm-cuda-12-4 py3-vllm-cuda-12-9 py3-vllm-cuda-13-0 request-1276 lmcache-cuda-12-8 +17
chainguard fixes for CVE-2026-54280
ReleasePackageFixed in
py3-13-scanner-test-libraries-aiohttp 0.0.1-r3
py3-vllm-cuda-12-4 0.18.1-r3
py3-vllm-cuda-12-9 0.19.1-r0
py3-vllm-cuda-13-0 0.20.2-r1
request-1276 0.29.0-r1
lmcache-cuda-12-8 0.5.3-r0

17 more rows

debian 4 releases · 1 package

affected 2 fixed 2
python-aiohttp
debian fixes for CVE-2026-54280
ReleasePackageFixed in
11 python-aiohttp affected
12 python-aiohttp 3.8.4-1+deb12u2
13 python-aiohttp affected
14 python-aiohttp 3.14.1-1

echo 1 release · 1 package

fixed 1
python-aiohttp
echo fixes for CVE-2026-54280
ReleasePackageFixed in
python-aiohttp 3.8.4-1+deb12u2

minimos 1 release · 10 packages

fixed 10
vllm-cu129 cassandra-medusa acapy-agent-1-6 litellm-1-84 litellm-1-85 litellm-1-86 +4
minimos fixes for CVE-2026-54280
ReleasePackageFixed in
vllm-cu129 +1 0.23.0-r0
cassandra-medusa 0.30.0-r0
acapy-agent-1-6 1.6.1-r0
litellm-1-84 1.84.6-r0
litellm-1-85 1.85.5-r0
litellm-1-86 1.86.5-r0

4 more rows

openSUSE Leap 1 release · 1 package

fixed 1
python313-aiohttp
openSUSE Leap fixes for CVE-2026-54280
ReleasePackageFixed inAdvisory
16.0 python313-aiohttp 3.11.16-160000.6.1 openSUSE-SU-2026:21372-1

wolfi 1 release · 2 packages

fixed 2
open-webui airflow-3
wolfi fixes for CVE-2026-54280
ReleasePackageFixed in
open-webui 0.9.6-r5
airflow-3 3.3.1-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.