Skip to content
Threat Brief

← All advisories

CVE-2026-19445

Critical 9.2No known exploitationFix available

Use-after-free of a server-side SSLContext when sni_callback switches contexts

Record last updated

CVSS score

9.2

Critical on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.7%

Higher than 53% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-416

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
mail.python.org (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Microsoftazl3 python3 3.12.14-2 on Azure Linux 3.0Not documented3.12.15-1Microsoft MSRC
Python Software FoundationCPythonfrom 3.11.0 before 3.11.173.11.17CVE Program
Python Software FoundationCPythonfrom 3.12.0 before 3.12.153.12.15CVE Program
Python Software FoundationCPythonfrom 3.13.0 before 3.13.163.13.16CVE Program
Python Software FoundationCPythonfrom 3.14.0 before 3.14.83.14.8CVE Program
Python Software FoundationCPythonfrom 3.15.0a1 before 3.15.0rc33.15.0rc3CVE Program
Python Software FoundationCPythonall versions before 3.10.223.10.22CVE Program

Timeline

  1. Disclosure

    CVE record published by PSF

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  6. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references