Aiohttp: Prior to 3.14.4, Set-Cookie parsing treats unrecognized name=value attributes as additional cookies, while
Affects aiohttpSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.14.4 when convenient.
Data as of 20 Nov 2026, 10:22 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 3.14.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/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/6963ee0befec1502b6bb7b4db6c72d044c08f4fa (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/b1f6c87b2bd3bd80f2b6c22ff46e11d00921e412 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13930 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13942 (opens in a new tab)
- github.com/aio-libs/aiohttp/security/advisories/GHSA-5pv8-vvhc-h7jv (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 the Set-Cookie parsing issue is fixed. Applying this official patch eliminates the vulnerability. No other mitigation is required.
Description
A vulnerability in aiohttp versions prior to 3.14.4 causes improper parsing of Set-Cookie headers, where unrecognized name=value attributes are treated as additional cookies. This behavior, combined with the CookieJar's lack of limits on stored or sent cookies, allows a malicious server to cause a client to accumulate a large number of cookies. This can lead to excessive memory and CPU consumption and the construction of very large Cookie headers on subsequent requests. The issue is resolved in aiohttp 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/6963ee0befec1502b6bb7b4db6c72d044c08f4fa (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/b1f6c87b2bd3bd80f2b6c22ff46e11d00921e412 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13930 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13942 (opens in a new tab)
- github.com/aio-libs/aiohttp/security/advisories/GHSA-5pv8-vvhc-h7jv (opens in a new tab)