Skip to main content
VulnerabilityPublished

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

Affects vdirsyncerSource GCVE Database

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

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

Data as of 17 Nov 2026, 17:36 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.21.0_2
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 vdirsyncer to 0.21.0_2.

Affected software

ProductAffectedFixed in
Homebrewvdirsyncerpkg:brew/vdirsyncerOther threatsAffected
  • >=0.19.0 <0.21.0_2
Fixed in
  • 0.21.0_2

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 in aiohttp version 0.21.0_2 that addresses this issue by limiting cookie storage and correcting Set-Cookie parsing behavior. Users should upgrade to version 0.21.0_2 or later to remediate this vulnerability.

Description

CVE-2026-128125 is a vulnerability in aiohttp's client CookieJar where unbounded cookie storage occurs due to improper Set-Cookie parsing. This allows 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.

References

Community reviews

Loading reviews…