Skip to main content
VulnerabilityPublished

CVE-2026-128126: AIOHTTP · Too many URL-encoded form fields block the event loop

Affects ssh-mitmSource GCVE Database

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

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

Data as of 17 Nov 2026, 17:48 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 6.0.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 ssh-mitm to 6.0.1.

Affected software

ProductAffectedFixed in
Homebrewssh-mitmpkg:brew/ssh-mitmOther threatsAffected
  • >=6.0.0 <6.0.1
Fixed in
  • 6.0.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 vulnerability is fixed in AIOHTTP version 6.0.1. Users should upgrade to version 6.0.1 or later to remediate this issue.

Description

AIOHTTP versions 6.0.0 up to but not including 6.0.1 contain a vulnerability where the Request.post() method does not limit the number of URL-encoded form fields. This allows an attacker to send a form POST with many repeated keys, causing quadratic time complexity in processing and blocking the event loop. This denial-of-service condition can be triggered within the default client_max_size limit. The issue is fixed in version 6.0.1.

References

Community reviews

Loading reviews…