Skip to main content
VulnerabilityPublished

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

Affects checkovSource GCVE Database

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

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

Data as of 17 Nov 2026, 18:49 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.3.30
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 checkov to 3.3.30.

Affected software

ProductAffectedFixed in
Homebrewcheckovpkg:brew/checkovOther threatsAffected
  • >=2.0.615 <3.3.30
Fixed in
  • 3.3.30

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

AI-suggested

A patch is available and should be applied by upgrading to AIOHTTP version 3.3.30 or later. Applying this official fix will prevent the unbounded cookie storage behavior. No additional mitigation steps are indicated by the vendor advisory.

Description

The AIOHTTP client CookieJar component had a vulnerability where it would parse unrecognized 'name=value' attributes in Set-Cookie headers as additional cookies without limiting the total number stored. This allowed a malicious server to cause the client to store an excessive number of cookies, leading to very large Cookie headers being sent on subsequent requests. This could result in excessive memory and CPU usage on the client side, especially when repeated on redirects. The issue affects versions from 2.0.615 up to but not including 3.3.30. A fix is available in version 3.3.30.

References

Community reviews

Loading reviews…