CVE-2026-124249: python3 security update
Affects python3Source GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.11.6-46.oe2403sp3 when convenient.
Data as of 19 Nov 2026, 02:56 UTC
Thin evidence
One scorer or none| CNA (PSF) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 3.11.6-46.oe2403sp3
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 18 Nov 2026.
What to do
Upgrade python3 to 3.11.6-46.oe2403sp3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
openEuler 24.03-LTS-SP3python3pkg:rpm/openEuler/python3&distro=openEuler-24.03-LTS-SP3Other 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 patch is available in Python version 3.11.6-46.oe2403sp3 that fixes this issue by enforcing cookie policy checks before deleting cookies. Users should upgrade to this fixed version or later to mitigate the vulnerability.
Description
A security vulnerability in Python's http.cookiejar.CookieJar module allowed a server to delete cookies belonging to other domains from a shared cookie jar by sending an expired Set-Cookie header. This occurred because the module used the Domain and Path attributes from the header without consulting the cookie policy. The issue was fixed by ensuring the cookie policy is consulted before an expired cookie can delete an existing one, in compliance with RFC 6265 section 5.3.