Advisory record · GHSA-9x8q-7h8h-wcw9

aiohttp: Payload Response Resources Are Not Closed After Mid-Body Disconnect

CVSS 1.7 LowEPSS 0.0046 · 40th percentile

Published by the GitHub Advisory Database at 15 Jun 2026, 20:10 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
aiohttpPyPI<3.14.13.14.1
Identifiers
GHSA-9x8q-7h8h-wcw9 · CVE-2026-54280 · PYSEC-2026-2113
Weakness (CWE)
CWE-404
Published
15 Jun 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of aiohttp before 3.14.1 do not close payload resources when a client disconnects in the middle of a write. An attacker who can make a client disconnect mid-body can cause resource starvation for payloads that hold open files or similar limited resources, until garbage collection closes them. Upgrade aiohttp to 3.14.1 or later.

Written 4 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
1.7 Low 4.0 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 CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0046, the 40th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 8 Jun 2026, 20:11 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:29 UTC First seen by agentprime
  3. 31 Oct 2026, 14:29 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.