Skip to main content
VulnerabilityPublished

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

Affects pferdSource GCVE Database

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

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

Data as of 17 Nov 2026, 17:50 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.10.0
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 pferd to 3.10.0.

Affected software

ProductAffectedFixed in
Homebrewpferdpkg:brew/pferdOther threatsAffected
  • >=3.4.2 <3.10.0
Fixed in
  • 3.10.0

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.10.0 or later, where this vulnerability is fixed. The patch is available and addresses the issue by enforcing proper size limits during multipart base64 part reading. No other mitigations are indicated.

Description

AIOHTTP versions from 3.4.2 up to but not including 3.10.0 contain a vulnerability in multipart handling where base64-encoded parts 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 size limits, potentially causing excessive memory consumption or event loop blocking. The issue is fixed in version 3.10.0.

References

Community reviews

Loading reviews…