Aiohttp: Prior to 3.14.4, Request.post() does not limit the number of fields in a URL-encoded form body, and inserting
Affects aiohttpSource GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 3.14.4 soon.
Data as of 20 Nov 2026, 10:21 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.7 |
|---|
- Patch
- Available – fixed in 3.14.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 19 Nov 2026.
What to do
Upgrade aiohttp to 3.14.4.
Patches and advisories
- github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/8b0100572936df28977b9de8a6cc7e464c0b521e (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13738 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13741 (opens in a new tab)
- github.com/aio-libs/aiohttp/security/advisories/GHSA-xgw8-8ccx-rmqh (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIaiohttppkg:pypi/aiohttpOther threats | Affected
| Fixed in
|
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.14.4 or later, where this issue is fixed. The vendor has released official patches and security advisories. No other mitigation is required once the upgrade is applied.
Description
Aiohttp versions prior to 3.14.4 have a vulnerability in the Request.post() method where there is no limit on the number of fields in a URL-encoded form body. This can cause the insertion of many repeated keys into a MultiDict to take quadratic time on the event loop, allowing a remote attacker to block the event loop by sending a specially crafted form POST request. The issue is fixed in version 3.14.4.
References
- github.com/aio-libs/aiohttp/releases/tag/v3.14.4 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/8b0100572936df28977b9de8a6cc7e464c0b521e (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13738 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13741 (opens in a new tab)
- github.com/aio-libs/aiohttp/security/advisories/GHSA-xgw8-8ccx-rmqh (opens in a new tab)