Skip to main content
VulnerabilityPublished

CVE-2026-54273: aio-libs aiohttp · Unthrottled Resource Allocation

Affects aio-libs aiohttpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.6 Medium : upgrade to 3.14.1 when convenient.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 4.0 base score
6.6Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.14.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade aio-libs aiohttp to 3.14.1.

Affected software

ProductAffectedFixed in
aio-libsaiohttpAffected
  • <3.14.1
Fixed in
  • 3.14.1
PyPIaiohttppkg:pypi/aiohttpOther threatsAffected
  • <3.14.1
Fixed in
  • 3.14.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade aiohttp to version 3.14.1 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated in the available data. Patch status is confirmed by the vendor stating the fix in 3.14.1.

Description

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, no limit was present on the number of pipelined requests that could be queued. An attacker may be able to use pipelined requests to use excessive amounts of memory, potentially leading to DoS. This vulnerability is fixed in 3.14.1.

References

Community reviews

Loading reviews…