http.cookiejar.CookieJar deleted a stored cookie when a response carried an already expired Set-Cookie header for it
Source GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.16.0 when convenient.
Data as of 9 Nov 2026, 16:36 UTC
Thin evidence
One scorer or none| CNA (PSF) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 3.16.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 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 9 Nov 2026.
What to do
Upgrade CPython to 3.16.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Python Software FoundationCPython | Affected
| Fixed in
|
GitHubCPythonpkg:github/CPythonOther 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
A fix is available that ensures the cookie policy is consulted before an expired cookie can delete an existing one, as required by RFC 6265 section 5.3. Users should update to the fixed version once available.
Description
The http.cookiejar.CookieJar component improperly deleted stored cookies when receiving a response with an already expired Set-Cookie header. This deletion occurred without consulting the cookie policy, allowing a server to potentially delete cookies from other domains within a shared cookie jar, such as urllib's HTTPCookieProcessor. The issue was fixed by ensuring the cookie policy is checked before allowing an expired cookie to delete an existing one, in compliance with RFC 6265 section 5.3.