Answer in brief
CVE-2026-19445 records a Critical severity (CVSS 9.2) vulnerability in Use-after-free of a server-side SSLContext when sni_callback switches contexts. The current sources do not mark it as known exploited. The current feed maps Python Software Foundation/CPython (generic), Python Software Foundation/CPython (generic), Python Software Foundation/CPython (generic), Python Software Foundation/CPython (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Python Software Foundation/CPython (generic), Python Software Foundation/CPython (generic), Python Software Foundation/CPython (generic), Python Software Foundation/CPython (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Python Software Foundation/CPythongeneric | >=0 <3.10.22 || >=3.11.0 <3.11.17 || >=3.12.0 <3.12.15 || >=3.13.0 <3.13.16 || >=3.14.0 <3.14.8 || >=3.15.0a1 <3.15.0 | 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8, 3.15.0 |
| Python Software Foundation/CPythongeneric | >=0 <3.10.22 || >=3.11.0 <3.11.17 || >=3.12.0 <3.12.15 || >=3.13.0 <3.13.16 || >=3.14.0 <3.14.8 || >=3.15.0a1 <3.15.0rc3 | 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8, 3.15.0rc3 |
| Python Software Foundation/CPythongeneric | >=0 <3.16.0 | 3.16.0 |
| Python Software Foundation/CPythongeneric | >=0 <3.15.0 | 3.15.0 |
| Python Software Foundation/CPythongeneric | >=0 <3.12.15 || >=3.13.0 <3.13.16 || >=3.14.0 <3.14.8 || >=3.15.0a1 <3.15.0 | 3.12.15, 3.13.16, 3.14.8, 3.15.0 |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)generic | >=V3.1.7 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)generic | >=V3.1.7 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)generic | >=V3.1.7 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)generic | >=V3.1.7 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)generic | >=V3.1.7 <* | * |
Published upstream
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 30, 2026
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 source text, attributed separately from HOL analysis.