HighGHSA-xgw8-8ccx-rmqhCVE-2026-128126

AIOHTTP: Too many URL-encoded form fields block the event loop

Published 16 Nov 2026 · Updated 16 Nov 2026

Is your project on an affected aiohttp?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<3.14.4
Fixed in
3.14.4
Update to the fixed version for your release line, for example:pip install 'aiohttp>=3.14.4'

Details

Summary

Request.post() had no limit on the number of fields in a URL-encoded form body. Inserting a large number of repeated keys into a MultiDict took quadratic time on the event loop.

Impact

An attacker could block the event loop with a form POST within the default client_max_size to any handler that calls Request.post().

---

Patch: https://github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53

Is GHSA-xgw8-8ccx-rmqh in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected aiohttp, and gives you the command that fixes it.

More advisories for aiohttp

  • HighCVE-2026-128124AIOHTTP: Event loop stall in add_domain() wildcard matching · 16 Nov 2026
  • MediumCVE-2026-128125AIOHTTP: Unbounded cookie storage in client CookieJar · 16 Nov 2026
  • HighCVE-2026-128127AIOHTTP: Base64 multipart parts bypass client_max_size · 16 Nov 2026
  • HighCVE-2026-128128AIOHTTP: WebSocket max_msg_size bypass via integer overflow · 16 Nov 2026
  • HighCVE-2026-128129AIOHTTP: Unbounded buffering of data received during an upgrade request · 16 Nov 2026
  • HighCVE-2026-128130AIOHTTP: Pure-Python parser request replay and buffer growth behind a declined upgrade · 16 Nov 2026
All 64 advisories for aiohttp

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.