Skip to main content
VulnerabilityPublished

CVE-2026-128125: AIOHTTP · Unbounded cookie storage in client CookieJar

Affects aiohttpSource GCVE Database

0
Compare
Authoritative record:CVE-2026-128125· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.14.4 when convenient.

Data as of 16 Nov 2026, 15:22 UTC

CVSS 4.0 base score
6.3Medium
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.06.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: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 15 Nov 2026.

What to do

Upgrade aiohttp to 3.14.4.

Affected software

ProductAffectedFixed in
PyPIaiohttpAffected
  • <3.14.4
Fixed in
  • 3.14.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade aiohttp to version 3.14.4 or later, where this vulnerability has been fixed. Applying this official fix eliminates the risk of unbounded cookie storage and the associated resource exhaustion.

Description

The aiohttp client library had a vulnerability in its CookieJar component where unbounded cookie storage could occur due to improper parsing of Set-Cookie headers. This allowed a malicious server to cause the client to store an excessive number of cookies, leading to large Cookie headers and excessive memory and CPU usage on the client side. This issue was fixed in version 3.14.4.

References

Community reviews

Loading reviews…