CVE-2026-19445: Use-after-free of a server-side SSLContext when sni_callback switches contexts
Noroxi assessment
Priority: Monitor (action score 36/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.52% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Python Software Foundation CPython 3.10.22, 3.11.17, 3.12.15; azl3 python3 3.12.14-2 on Azure Linux 3.0 3.12.15-1.
Low priority for now. Upgrade to Python Software Foundation CPython 3.10.22, 3.11.17, 3.12.15; azl3 python3 3.12.14-2 on Azure Linux 3.0 3.12.15-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- EUVD-2026-90077
- ALSA-2026:77017
- ALSA-2026:77018
- ALSA-2026:77020
- ALSA-2026:77021
- ALSA-2026:77028
- ALSA-2026:85239
- ALSA-2026:89742
- openSUSE-SU-2026:12069-1
- openSUSE-SU-2026:12087-1
- openSUSE-SU-2026:12121-1
- openSUSE-SU-2026:12122-1
- openSUSE-SU-2026:12123-1
- openSUSE-SU-2026:12124-1
- openSUSE-SU-2026:12477-1
- RHSA-2026:74867
- RHSA-2026:77017
- RHSA-2026:77018
- RHSA-2026:77020
- RHSA-2026:77021
- Published
- Sep 30, 2026
- Updated
- Nov 9, 2026
- EPSS
- 0.5% · 44th percentile
- CWE
- CWE-416
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 36 / 40 · 9.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · PSF
- 9.2
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (PSF). Independent of NVD's CPE analysis and usually ahead of it.
Python Software Foundation CPython
- before 3.10.22affected · python
- 3.11.0 and later · before 3.11.17affected · python
- 3.12.0 and later · before 3.12.15affected · python
- 3.13.0 and later · before 3.13.16affected · python
- 3.14.0 and later · before 3.14.8affected · python
- 3.15.0a1 and later · before 3.15.0rc3affected · python
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | python-unversioned-command | before 3.12.15-1.el10_2 | 3.12.15-1.el10_2 |
| AlmaLinux:10 | python3 | before 3.12.15-1.el10_2 | 3.12.15-1.el10_2 |
| AlmaLinux:10 | python3-debug | before 3.12.15-1.el10_2 | 3.12.15-1.el10_2 |
| AlmaLinux:10 | python3-devel | before 3.12.15-1.el10_2 | 3.12.15-1.el10_2 |
| AlmaLinux:10 | python3-idle | before 3.12.15-1.el10_2 | 3.12.15-1.el10_2 |
| AlmaLinux:10 | python3-libs | before 3.12.15-1.el10_2 | 3.12.15-1.el10_2 |
| AlmaLinux:10 | python3-test | before 3.12.15-1.el10_2 | 3.12.15-1.el10_2 |
| AlmaLinux:10 | python3-tkinter | before 3.12.15-1.el10_2 | 3.12.15-1.el10_2 |
| AlmaLinux:10 | python3.14 | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-debug | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-devel | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-freethreading | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-freethreading-debug | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-freethreading-devel | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-freethreading-idle | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-freethreading-libs | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-freethreading-test | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-freethreading-tkinter | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-idle | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-libs | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-test | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:10 | python3.14-tkinter | before 3.14.8-1.el10_2 | 3.14.8-1.el10_2 |
| AlmaLinux:8 | platform-python | before 3.6.8-79.el8_10.alma.1 | 3.6.8-79.el8_10.alma.1 |
| AlmaLinux:8 | platform-python-debug | before 3.6.8-79.el8_10.alma.1 | 3.6.8-79.el8_10.alma.1 |
+96
Same product
python software foundation: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-115557Distrust compromised intermediate certificates in ssl module37Monitor
- CVE-2025-4517Arbitrary writes via tarfile realpath overflow37Monitor
- CVE-2026-6100Use-after-free in lzma.LZMADecompressor, bz2.BZ2Decompressor, and gzip.GzipFile after re-use under memory pressure36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-82049Sep 14, 2026 · tarfile extraction filters allow file modification and content disclosure via hard link to symlink33Monitor
- ← EarlierCVE-2026-12345Sep 29, 2026 · Race condition in tempfile.TemporaryDirectory cleanup allows deleting files outside the temporary directory23Monitor
- Later →CVE-2026-19553Sep 30, 2026 · SSLContext.wrap_bio() missing validation of server_hostname parameter30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Python Software Foundation CPython | 3.10.22 | Vendor (CNA) |
| Python Software Foundation CPython | 3.11.17 | Vendor (CNA) |
| Python Software Foundation CPython | 3.12.15 | Vendor (CNA) |
| Python Software Foundation CPython | 3.13.16 | Vendor (CNA) |
| Python Software Foundation CPython | 3.14.8 | Vendor (CNA) |
| Python Software Foundation CPython | 3.15.0rc3 | Vendor (CNA) |
| azl3 python3 3.12.14-2 on Azure Linux 3.0 | 3.12.15-1 · Release Notes | Microsoft (MSRC) |
| almalinux:python3.12 | 3.12.15-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:python3.12 | 3.12.15-2.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3.12-debug | 3.12.15-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:python3.12-debug | 3.12.15-2.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3.12-devel | 3.12.15-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:python3.12-devel | 3.12.15-2.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3.12-idle | 3.12.15-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:python3.12-idle | 3.12.15-2.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3.12-libs | 3.12.15-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:python3.12-libs | 3.12.15-2.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3.12-rpm-macros | 3.12.15-2.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3.12-test | 3.12.15-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:python3.12-test | 3.12.15-2.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3.12-tkinter | 3.12.15-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:python3.12-tkinter | 3.12.15-2.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:python3.14 | 3.14.8-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:python3.14-debug | 3.14.8-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:python3.14-devel | 3.14.8-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:python3.14-freethreading | 3.14.8-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:python3.14-freethreading-debug | 3.14.8-1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| alpine:python3 | 3.12.15-r0 · Alpine:v3.21 | Package registry (OSV) |
| debian:pypy3 | 8.0.1+dfsg-1 · Debian:14 | Package registry (OSV) |
| debian:python3.11 | 3.11.2-6+deb12u9 · Debian:12 | Package registry (OSV) |
+39
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-02 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- First PoC+1 d
- TodayNov 10, 2026+40 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Gregory P. Smith (https://github.com/gpshead)reporter
- Seth Larson (https://github.com/sethmlarson)coordinator
- Bénédikt Tran (https://github.com/picnixz)remediation reviewer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-6100170 days apartUse-after-free in lzma.LZMADecompressor, bz2.BZ2Decompressor, and gzip.GzipFile after re-use under memory pressure36Monitor
- CVE-2025-4516503 days apartUse-after-free in "unicode_escape" decoder with error handler23Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Exploit maturitynone → poc
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- github.com/python/cpython/commit/46133cd57d309652139ada74014aca7665ac552b
- github.com/python/cpython/commit/63fab143d94cafae71850831acfb52041ba44af7
- github.com/python/cpython/commit/b12968cefe69ca1dcb8606c832ff73ee7dbf4ba8
- github.com/python/cpython/commit/cd7e51e7d4563866fbaa1e2521ae69b45daf3698
- github.com/python/cpython/commit/d8717ed01717a9641686e6e6f83f0ab8af235e2c
- github.com/python/cpython/commit/ec44b5a3258cbda947d5e07242ee562ed05ef24b
- github.com/python/cpython/issues/156293
- github.com/python/cpython/pull/158504
- mail.python.org/archives/list/security-announce@python.org/thread/QMQIUQB6WGGC3MI7I3WKQXOYOBDSPPS3/
- www.openwall.com/lists/oss-security/2026/09/30/17
Vendor advisories and official records. Exploit/PoC links are deliberately left out.