Skip to main content
CVE-2026-19445VulnerabilityPublished Updated

A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-19445· Critical 9.2

Not known to be exploited · CVSS 9.2 Critical · fixed in 3.15.0rc3 : patch CPython as a priority.

Data as of 10 Nov 2026, 16:36 UTC

CVSS 4.0 base score
9.2Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (PSF)CVSS 4.09.2
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 10 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
Python Software FoundationCPythonAffected
  • >=3.15.0a1 <3.15.0rc3
Fixed in
  • 3.15.0rc3
Python Software FoundationCPythonAffected
  • >=3.14.0 <3.14.8
Fixed in
  • 3.14.8
Python Software FoundationCPythonAffected
  • >=3.13.0 <3.13.16
Fixed in
  • 3.13.16
Python Software FoundationCPythonAffected
  • >=3.12.0 <3.12.15
Fixed in
  • 3.12.15
Python Software FoundationCPythonAffected
  • >=3.11.0 <3.11.17
Fixed in
  • 3.11.17
Python Software FoundationCPythonAffected
  • <3.10.22
Fixed in
  • 3.10.22

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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

Community reviews

Loading reviews…