Skip to main content
CVE-2026-128127VulnerabilityPublished Updated

Aiohttp: Prior to 3.14.4, BodyPartReader.read_chunk() processing a multipart part with Content-Transfer-Encoding set

Affects aiohttpSource GCVE Database

0
Compare
Authoritative record:CVE-2026-128127· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 3.14.4 soon.

Data as of 20 Nov 2026, 10:21 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 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 19 Nov 2026.

What to do

Upgrade aiohttp to 3.14.4.

Affected software

ProductAffectedFixed in
PyPIaiohttppkg:pypi/aiohttpOther threatsAffected
  • <3.14.4
Fixed in
  • 3.14.4

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

Community reviews

Loading reviews…