Aiohttp: Prior to 3.14.4, BodyPartReader.read_chunk() processing a multipart part with Content-Transfer-Encoding set
Affects aiohttpSource GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 3.14.4 soon.
Data as of 20 Nov 2026, 10:21 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.7 |
|---|
- Patch
- Available – fixed in 3.14.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 19 Nov 2026.
What to do
Upgrade aiohttp to 3.14.4.
Patches and advisories
- github.com/aio-libs/aiohttp/commit/2d9c5c1062eff0034fb3ab120897a6c1b3ff7041 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/a555ab698e08e9baea7386d5b4c0761cb8956fdd (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13509 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13513 (opens in a new tab)
- github.com/aio-libs/aiohttp/security/advisories/GHSA-24c4-3p7v-29cm (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIaiohttppkg:pypi/aiohttpOther threats | Affected
| Fixed in
|
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.4 or later, where this issue is fixed. The vendor has released patches and security advisories addressing this vulnerability.
Description
A vulnerability in aiohttp prior to version 3.14.4 allows a remote attacker to bypass client_max_size limits by sending a specially crafted multipart request with Content-Transfer-Encoding set to base64. The BodyPartReader.read_chunk() method improperly handles such requests, potentially causing excessive memory consumption or event loop spinning. This issue is fixed in version 3.14.4.
References
- github.com/aio-libs/aiohttp/releases/tag/v3.14.4 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/2d9c5c1062eff0034fb3ab120897a6c1b3ff7041 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/a555ab698e08e9baea7386d5b4c0761cb8956fdd (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13509 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13513 (opens in a new tab)
- github.com/aio-libs/aiohttp/security/advisories/GHSA-24c4-3p7v-29cm (opens in a new tab)