Skip to main content
VulnerabilityPublished

CVE-2026-128127: AIOHTTP · Base64 multipart parts bypass client_max_size

Affects blackSource GCVE Database

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

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

Data as of 17 Nov 2026, 19:49 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 26.10.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

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 16 Nov 2026.

What to do

Upgrade black to 26.10.1.

Affected software

ProductAffectedFixed in
Homebrewblackpkg:brew/blackOther threatsAffected
  • >=19.10b0_3 <26.10.1
Fixed in
  • 26.10.1

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

AI-suggested

A patch is available and the issue is fixed in aiohttp version 26.10.1. Users should upgrade to version 26.10.1 or later to remediate this vulnerability.

Description

A vulnerability in aiohttp's multipart handling allows bypassing the client_max_size limit when processing parts encoded with base64. The BodyPartReader.read_chunk() method reads until the chunk length is a multiple of 4 without enforcing size limits, potentially causing excessive memory consumption or event loop blocking. This affects aiohttp versions from 19.10b0_3 up to but not including 26.10.1. The issue is fixed in version 26.10.1.

References

Community reviews

Loading reviews…