Skip to content

ApplicationsCritical 9.2Patch available

CVE-2026-19445

CPython SSLContext SNI callback use-after-free can crash or corrupt servers.

How scary is it?

updated 10 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • Yes

    Proof-of-concept code is public2

    1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list3

    Not in the catalog as of our last sync.

Scare-o-meter

Act this week

Serious and within reach of attackers. Schedule the fix this week.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: Public proof-of-concept code exists for a network-reachable flaw; CVSS 9.2.1 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run one of these 3 products in an affected versionPython Software Foundation CPython / libpython / Python

    Python Software Foundation CPython: < 3.12.15, >= 3.13.0 and < 3.13.16, >= 3.14.0 and < 3.14.8, >= 3.15.0a1 and < 3.15.0

    libpython: < 3.10.22, >= 3.11.0 and < 3.11.17, >= 3.12.0 and < 3.12.15, >= 3.13.0 and < 3.13.16 (+1 more)

    Python: < 3.10.22, >= 3.11.0 and < 3.11.17, >= 3.12.0 and < 3.12.15, >= 3.13.0 and < 3.13.16 (+1 more)

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. Specific conditions are met that the attacker does not control

    CVSS attack complexity: High (AC:H). Needs specific conditions, a race or a particular configuration. The CVE record does not always say which.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per the vendorUpgrade to a fixed release3.10.22 / 3.11.17 / 3.12.15 / 3.13.16 (+1 more)

    libpython: 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8

    Python: 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8

    Fixed releases as stated by the vendor in the CVE record.

    See the affected products table · Source 1

  2. Recommendation, AI-writtenUpgrade CPython to patched release; ensure SSLContext objects with sni_callback are kept alive.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Affects CPython's stdlib TLS handling—widely used runtime. Remote unauthenticated clients can crash or trigger use-after-free; could disrupt many Python servers and services.

CVSS
9.2Criticalscored by the publisher (CNA)
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
0.68%chance of exploitation in the next 30 daystop 47% of scored CVEsFIRST score of 21 Nov 2026
Fix
Fixed in 3.10.22, 3.11.17, 3.12.15per the vendor; 2 more listed below
Published
30 Sept 2026analysed here 1 Oct 2026

Do first. Upgrade to a fixed release: 3.10.22, 3.11.17, 3.12.15, 3.13.16 (and 1 more below).

Summary

Impact

Remote unauthenticated TLS client can crash servers or trigger use-after-free by swapping SSLContext via sni_callback, enabling DoS or potential RCE.

Triage

Attack surface
Server-side
Exploitable
At runtime
Weakness
Can a WAF block it?
No. See why

Executive summary (AI-written)

CVE-2026-19445 is a critical vulnerability affecting the CPython SSL module, which could lead to significant disruptions for businesses relying on Python-based applications. Executing this vulnerability may allow a remote unauthenticated client to crash servers or even exploit use-after-free scenarios, potentially enabling remote code execution (RCE). Given that many organizations utilize Python for their server-side applications, this presents a high-level risk that could lead to service interruption or unauthorized access to sensitive data. Immediate action is required to mitigate the risks posed by this vulnerability, as it has been assigned a CVSS score of 9.2, indicating a major severity level. Organizations must prioritize upgrading their CPython to the patched version and review their SSLContext implementations to ensure that SNI callbacks are properly managed. Failure to address this vulnerability could have serious operational and financial repercussions, making it crucial for decision-makers to act swiftly to protect their systems.

Technical analysis (AI-written)

CVE-2026-19445 is classified with a CVSS score of 9.2, reflecting its severe impact on systems utilizing the CPython SSL module. This vulnerability arises from a use-after-free condition triggered when a remote unauthenticated TLS client manipulates SSLContext objects through the SNI (Server Name Indication) callback. The exploit can result in a denial-of-service (DoS) by crashing the server, or in some configurations, could lead to remote code execution (RCE) if an attacker can manipulate memory states post-exploitation. The vulnerability primarily affects Python applications that create per-connection SSLContext objects utilizing the `sni_callback`. Attackers could exploit this by sending specially crafted TLS requests that swap SSLContext instances, thus causing the server to either malfunction or expose itself to code execution vulnerabilities. As Python is a widely adopted programming language across various industries, the ramifications of this vulnerability could be substantially felt, potentially impacting a large number of systems and services. To exploit this vulnerability, an attacker requires no authentication, increasing the attractiveness of the exploit. The complexity of the attack is relatively low given the broad distribution of Python environments and the nature of the SSL/TLS protocols. Therefore, organizations should consider the risk of exposure, particularly those deploying web servers or applications that handle untrusted data. Mitigation involves immediate upgrading to the patched version of CPython. It’s also vital for developers to ensure that SSLContext objects associated with SNI callbacks are held in scope for the duration of their use, thus preventing premature deallocation and the subsequent potential for use-after-free conditions. Additionally, organizations should review their overall SSL/TLS implementation strategies and consider implementing strict input validation and security controls around TLS handshakes. In terms of broader risk management, organizations should include this vulnerability in their ongoing security assessments and vulnerability management frameworks. Regular patch management routines must be enforced, and security teams must monitor for unusual patterns in server behavior that may indicate exploitation attempts of this vulnerability. Regular audits and reviews of code quality concerning SSL/TLS usage will also help in fortifying defenses against similar vulnerabilities in the future.

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.

Affected products

ProductAffected versions
Python Software Foundation CPython< 3.12.15>= 3.13.0 and < 3.13.16>= 3.14.0 and < 3.14.8>= 3.15.0a1 and < 3.15.0Vendor says fixed in: not stated
libpythonfrom the Bitnami advisory, via OSV< 3.10.22>= 3.11.0 and < 3.11.17>= 3.12.0 and < 3.12.15>= 3.13.0 and < 3.13.16>= 3.14.0 and < 3.14.8Vendor says fixed in: 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8
Pythonfrom the Bitnami advisory, via OSV< 3.10.22>= 3.11.0 and < 3.11.17>= 3.12.0 and < 3.12.15>= 3.13.0 and < 3.13.16>= 3.14.0 and < 3.14.8Vendor says fixed in: 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8

As published in the CVE Program record, and, for products that ship the affected component, in the advisory named beside them. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • CPython ssl module
  • Python servers using sni_callback
  • Apps creating per-connection SSLContext

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. The vulnerability involves the SSLContext SNI callback in Python's SSL module, which is triggered during SSL/TLS handshake over the network, not via HTTP requests. Therefore, a web application firewall cannot filter or block the attack.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
CISA SSVC
exploitation none, automatable no, technical impact totalAssessed by CISA 9 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 30 Sept 2026Published
  2. 1 Oct 2026Analysed by vulneraibility.com1 day later
  3. 2 Oct 2026First proof-of-concept repository on GitHub (unvetted)1 day later
  4. 9 Nov 2026CISA SSVC assessment: exploitation none39 days later
  5. 10 Nov 2026CVE record last updated1 day later

Common questions

Is CVE-2026-19445 being exploited?

Not confirmed. CVE-2026-19445 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.68% probability of exploitation in the next 30 days.

How severe is CVE-2026-19445?

CVE-2026-19445 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-19445?

Yes. A fix has been recorded for CVE-2026-19445. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-19445 affect?

CVE-2026-19445 affects CPython ssl module, Python servers using sni_callback, Apps creating per-connection SSLContext. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-19445?

Upgrade CPython to patched release; ensure SSLContext objects with sni_callback are kept alive.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

12 references in the CVE record, grouped by the tags the record gives them.

Advisories (1)

Patches (8)

  • github.com /python/cpython/pull/158504
  • github.com /python/cpython/commit/34a53dce8174da2fceb12fe084a4def02a10053d
  • github.com /python/cpython/commit/46133cd57d309652139ada74014aca7665ac552b
  • github.com /python/cpython/commit/63fab143d94cafae71850831acfb52041ba44af7
  • github.com /python/cpython/commit/cd7e51e7d4563866fbaa1e2521ae69b45daf3698
  • github.com /python/cpython/commit/d8717ed01717a9641686e6e6f83f0ab8af235e2c
Show 2 more
  • github.com /python/cpython/commit/b12968cefe69ca1dcb8606c832ff73ee7dbf4ba8
  • github.com /python/cpython/commit/ec44b5a3258cbda947d5e07242ee562ed05ef24b

Other links (3)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.