CVE-2026-19445: Python Software Foundation CPython · Use After Free
Affects Python Software Foundation CPythonSource CVE Database V5
Not known to be exploited · CVSS 9.2 Critical · fixed in 3.15.0rc3 : patch Python Software Foundation CPython as a priority.
Data as of 14 Nov 2026, 20:58 UTC
Thin evidence
One scorer or none| CNA (PSF) | CVSS 4.0 | 9.2 |
|---|
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.15.0rc3, 3.14.8, 3.13.16 +3
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | Affected
| Fixed in
|
| Python Software FoundationCPython | 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
Apply the official fixes available in CPython versions 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8, and 3.15.0rc3 or later. Until patched, ensure that the server maintains a reference to every SSLContext that sets sni_callback for the lifetime of the server to prevent the use-after-free condition.
Description
A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback assigns a different context to SSLSocket.context (the documented way to select a certificate per server name) and nothing else keeps the original ssl.SSLContext alive. Typical cases are servers that create an SSLContext per connection or replace it while connections are open; servers that wrap their listening socket with it are not affected. Mitigation: keep a reference to every SSLContext that sets sni_callback for the lifetime of the server. TLS clients are not affected.
References
- github.com/python/cpython/pull/158504 (opens in a new tab)
- mail.python.org/archives/list/security-announce@python.org/thread/QMQIUQB6WGGC3MI7I3WKQXOYOBDSPPS3/ (opens in a new tab)
- github.com/python/cpython/issues/156293 (opens in a new tab)
- openwall.com/lists/oss-security/2026/09/30/17 (opens in a new tab)
- github.com/python/cpython/commit/34a53dce8174da2fceb12fe084a4def02a10053d (opens in a new tab)
- github.com/python/cpython/commit/46133cd57d309652139ada74014aca7665ac552b (opens in a new tab)
- github.com/python/cpython/commit/63fab143d94cafae71850831acfb52041ba44af7 (opens in a new tab)
- github.com/python/cpython/commit/cd7e51e7d4563866fbaa1e2521ae69b45daf3698 (opens in a new tab)
- github.com/python/cpython/commit/d8717ed01717a9641686e6e6f83f0ab8af235e2c (opens in a new tab)
- github.com/python/cpython/commit/b12968cefe69ca1dcb8606c832ff73ee7dbf4ba8 (opens in a new tab)
- github.com/python/cpython/commit/ec44b5a3258cbda947d5e07242ee562ed05ef24b (opens in a new tab)
- cert-portal.siemens.com/productcert/html/ssa-457936.html (opens in a new tab)