Skip to main content
VulnerabilityPublished

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

Affects codelimitSource GCVE Database

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

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

Data as of 17 Nov 2026, 19:34 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 0.7.0
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 16 Nov 2026.

What to do

Upgrade codelimit to 0.7.0.

Affected software

ProductAffectedFixed in
Homebrewcodelimitpkg:brew/codelimitOther threatsAffected
  • >=0.6.0 <0.7.0
  • >=0.8.0
Fixed in
  • 0.7.0

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

AI-suggested

A fix for this vulnerability is available in AIOHTTP version 0.7.0. Users should upgrade to version 0.7.0 or later to mitigate this issue.

Description

AIOHTTP's client CookieJar had a vulnerability where unrecognized Set-Cookie attributes caused additional cookies to be stored without limit. This allowed a malicious server to cause excessive memory and CPU usage on the client by making it store a very large number of cookies, resulting in oversized Cookie headers on subsequent requests. The issue was fixed in version 0.7.0.

References

Community reviews

Loading reviews…