Python Software Foundation · Python (CPython) · published 2026-09-30
CVE-2026-19445Use-after-free of a server-side SSLContext when sni_callback switches contexts
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-19445 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 45% of all CVEs. This Python (CPython) vulnerability: CVSS 9.2 (v4.0), a successful attack gives total control of the component. Fixed upstream in Python (CPython) 3.14.8, 3.13.16, 3.12.15, 3.11.17 (+1 more); patched packages are out for Debian; Ubuntu still has unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Python (CPython) 3.14.8, 3.13.16, 3.12.15, 3.11.17, 3.10.22.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | pypy3 | Won’t fix |
| 13 trixie | python3.13 | Won’t fix | |
| 12 bookworm | pypy3 | Won’t fix | |
| 12 bookworm | python3.11 | Fixed in 3.11.2-6+deb12u9 | |
| Ubuntu | 26.04 LTS | python3.14 | No fix yet |
| 24.04 LTS | python3.12 | No fix yet | |
| 22.04 LTS | python3.10 | No fix yet | |
| Red Hat Enterprise Linux (+11 more packages) | RHEL 9 | python3.11 | Won’t fix |
| RHEL 8 | python3.11 | Won’t fix |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Language runtimePython (CPython)
Python (CPython) security releases: 3.14.8, 3.13.16, 3.12.15, 3.11.17, 3.10.22
Upgrade to
3.14.83.13.163.12.153.11.173.10.22Why: CVE-2026-15806: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.5% (45th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.2 (v4.0)CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Affected versions (from the CVE record)#
- Python Software Foundation CPython
0to before3.10.22(affected)3.11.0to before3.11.17(affected)3.12.0to before3.12.15(affected)3.13.0to before3.13.16(affected)3.14.0to before3.14.8(affected)3.15.0a1to before3.15.0rc3(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.