Vulnerability Intelligence Report
Use-after-free of a server-side SSLContext when sni_callback switches contexts
CVE-2026-19445
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.
No Active Exploit Signals
CVSS Base Score
9.2
CRITICAL
EPSS Probability:0.51%
Executive Threat Verdict
Evaluating...
Evaluating Threat Landscape...
Assessing known weaponization, exploitation telemetry, and federal advisories.
Attack Surface
—
Authentication
—
Weaponization
—
SSVC Action
—
Weaknesses (CWE)
CWE-416 ↗CWE-416
Affected Products & Versions
| Vendor | Product | Affected Versions |
|---|---|---|
| Python Software Foundation | CPython | 0 < 3.10.22 (affected), 3.11.0 < 3.11.17 (affected), 3.12.0 < 3.12.15 (affected), 3.13.0 < 3.13.16 (affected), 3.14.0 < 3.14.8 (affected), 3.15.0a1 < 3.15.0 (affected) |
References & Technical Advisories
No reference links found.
Threat Intelligence Signals
EPSS Score
0.512%
GitHub Advisory
Identity & Timeline
| Status | PUBLISHED |
| Assigning Authority | Python Software Foundation · Vendor · USA |
| Reserved | 2026-08-10T13:31:21 |
| Published | 2026-09-30T16:16:04 |
| Last Updated | 2026-10-02T00:38:47 |
Community Chatter & Buzz