Skip to main content
VulnerabilityPublished

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

Affects otterdogSource GCVE Database

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

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

Data as of 17 Nov 2026, 19:07 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 1.6.1_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 otterdog to 1.6.1_1.

Affected software

ProductAffectedFixed in
Homebrewotterdogpkg:brew/otterdogOther threatsAffected
  • >=1.0.1 <1.6.1_1
Fixed in
  • 1.6.1_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 should be applied by upgrading AIOHTTP to version 1.6.1_1 or later. This update corrects the multipart base64 handling to enforce size limits properly, preventing the bypass. No additional mitigation is required if the patch is applied.

Description

AIOHTTP versions from 1.0.1 up to but not including 1.6.1_1 contain a vulnerability where multipart parts encoded with base64 can bypass the client_max_size limit. This occurs because the BodyPartReader.read_chunk() method reads until the chunk length is a multiple of 4 without enforcing a byte limit, allowing an attacker to cause excessive memory consumption or event loop blocking by sending specially crafted multipart requests. The issue is fixed in version 1.6.1_1.

References

Community reviews

Loading reviews…