AIOHTTP: Payload Response Resources Are Not Closed After Mid-Body Disconnect
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-54280
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 11:19 UTC · Revision 1
Source evidence
AIOHTTP: Payload Response Resources Are Not Closed After Mid-Body Disconnect
core-osv · Original sourcePublished 22 Jun 2026, 16:40 UTC
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.
osv:CVE-2026-54280
Complete source record
{
"id": "ec81c9c365658d9456642faa67648d6d4214b7b93548c7b1f354e02de1029787",
"url": "https://osv.dev/vulnerability/CVE-2026-54280",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "AIOHTTP: Payload Response Resources Are Not Closed After Mid-Body Disconnect",
"summary": "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.",
"evidence": "osv:CVE-2026-54280",
"products": [],
"severity": "low",
"structured": {
"id": "CVE-2026-54280",
"aliases": [
"CVE-2026-54280",
"GHSA-9x8q-7h8h-wcw9",
"PYSEC-2026-2113"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/aio-libs/aiohttp",
"type": "GIT",
"events": [
{
"introduced": "152e4160fde8985e770398da5271396d7a831198"
},
{
"fixed": "9c35d03aa5fecd294510196e07f176f1a2e7fa33"
},
{
"fixed": "a762eda5242f6490d6ba667533193f8b473ad587"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:aiohttp:aiohttp:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "3.12.1"
},
{
"fixed": "3.14.1"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "a762eda5242f6490d6ba667533193f8b473ad587"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-54280.json"
}
}
],
"modified": "2026-10-28T02:30:34.477372290Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54280.json",
"https://github.com/aio-libs/aiohttp/security/advisories/GHSA-9x8q-7h8h-wcw9",
"https://nvd.nist.gov/vuln/detail/CVE-2026-54280",
"https://github.com/aio-libs/aiohttp/commit/a762eda5242f6490d6ba667533193f8b473ad587"
],
"provider_metadata": {
"cwe_ids": [
"CWE-404"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/54xxx/CVE-2026-54280.json"
}
},
"related_cves": [
{
"value": "CVE-2026-54280",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 501990,
"published_at": "2026-06-22T16:40:23.157+00:00"
}