CVE-2026-19445

CRITICALPre-NVD 9.29.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — Patch released this week

Also known asEUVD-2026-90077 (ENISA EUVD) · GHSA-7jvw-f348-84gq (GitHub Security Advisories)Source: ENISA EUVD

9.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS
9.2
EG Score
9.2CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity92% × 45%
Impact severity (EG Severity): CVSS 9.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.2): severity, escalated by confirmed exploitation. This CVE's 9.2 is its impact severity (EG Severity), not escalated.

EG Severity
9.2 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 30, 2026

Last Modified

November 10, 2026

Advisory Details (3)

Auto-updated Sep 30, 2026
Patch available. Sources: github_pr.
Web page

Use-after-free for server-side SSLContext with sni_callback · Issue #156293 · python/cpython · GitHub

https://github.com/python/cpython/issues/156293
Web page

Mailman 3 [CVE-2026-19445] Use-after-free of a server-side SSLContext when sni_callback switches contexts - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/QMQIUQB6WGGC3MI7I3WKQXOYOBDSPPS3/
GitHub pull request

gh-156293: Use-after-free for server-side SSLContext with sni_callback

Fix merged in python/cpython PR #158504 on 2026-09-30 — awaiting tagged release

https://github.com/python/cpython/pull/158504

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython3.9-0:3.9.21-2.el9_6.82026-11-20redhat
redhatpython3.9-0:3.9.18-3.el9_4.152026-11-20redhat
redhatpython3.9-0:3.9.16-1.el9_2.162026-11-20redhat
redhatpython3-0:3.6.8-51.el8_8.182026-11-19redhat
oraclepatch2026-11-17oracle
redhatpython3.9-0:3.9.25-14.el9_92026-11-11redhat
redhatpython3-0:3.6.8-39.el8_4.132026-11-04redhat
redhatdiscovery/discovery-ui-rhel9:17937337162026-11-04redhat
redhatpython3-0:3.6.8-47.el8_6.162026-11-03redhat
redhatpython3.9-0:3.9.25-7.el9_8.62026-10-26redhat
redhatcostmanagement/costmanagement-ui-rhel10:17926052722026-10-21redhat
redhatpython3-0:3.6.8-79.el8_102026-10-19redhat
redhatrhui5/rhua-rhel9:17919786932026-10-14redhat
redhatpython3.14-0:3.14.8-1.el10_22026-10-08redhat
redhatpython3.14-0:3.14.8-1.el9_82026-10-08redhat
redhatpython3.12-0:3.12.15-1.el10_22026-10-08redhat
redhatpython3.12-0:3.12.15-1.el9_82026-10-08redhat
redhatpython3.12-0:3.12.15-2.el8_102026-10-07redhat
redhatpython3-15-main-3.15.0~rc2-1.1.hum12026-10-02redhat

These rows come from Red Hat and Oracle. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(12 across 7 ecosystems)
Debian:14(4)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.19+dfsg-2 ... 8.0.0+dfsg-1 (13 versions)
  • every version up to 8.0.1+dfsg-1: fixed in 8.0.1+dfsg-1
—
python3.133.13.11-1 ... 3.13.9-1 (9 versions)
  • every version on: no fix on record
—
python3.143.14.0-1 ... 3.14.7-5 (29 versions)
  • every version up to 3.14.8-1: fixed in 3.14.8-1
—
python3.153.15.0~a8-1 ... 3.15.0~rc2-3 (12 versions)
  • every version up to 3.15.0~rc3-1: fixed in 3.15.0~rc3-1
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.11+dfsg-2 ... 8.0.1+dfsg-1 (32 versions)
  • every version on: no fix on record
—
python3.113.11.2-6 ... 3.11.2-6+deb12u8 (9 versions)
  • every version up to 3.11.2-6+deb12u9: fixed in 3.11.2-6+deb12u9
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
pypy37.3.19+dfsg-2 ... 8.0.1+dfsg-1 (14 versions)
  • every version on: no fix on record
—
python3.133.13.11-1 ... 3.13.9-1 (15 versions)
  • every version on: no fix on record
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.15-r0: fixed in 3.12.15-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.15-r0: fixed in 3.12.15-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.12.15-r0: fixed in 3.12.15-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
python3—
  • every version up to 3.14.8-r0: fixed in 3.14.8-r0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 99× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 344 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 244 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 06:39 UTCVendor advisory
  2. 2026-11-21 22:59 UTCEchelonGraph re-scored
  3. 2026-11-21 22:59 UTCVendor advisory
  4. 2026-11-21 22:59 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  5. 2026-11-21 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  6. 2026-11-20 23:08 UTCEchelonGraph re-scored
  7. 2026-11-20 23:08 UTCVendor advisory
  8. 2026-11-20 23:08 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  9. 2026-11-20 16:37 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  10. 2026-11-19 23:17 UTCEchelonGraph re-scored
  11. 2026-11-19 23:17 UTCVendor advisory
  12. 2026-11-19 23:17 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  13. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  14. 2026-11-19 03:00 UTCEchelonGraph re-scored
  15. 2026-11-19 03:00 UTCVendor advisory
  16. 2026-11-19 03:00 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  17. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  18. 2026-11-18 03:09 UTCEchelonGraph re-scored
  19. 2026-11-18 03:09 UTCVendor advisory
  20. 2026-11-18 03:09 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  21. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  22. 2026-11-17 03:18 UTCEchelonGraph re-scored
  23. 2026-11-17 03:18 UTCVendor advisory
  24. 2026-11-17 03:18 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  25. 2026-11-16 16:49 UTCEPSS rescoreEPSS 0.5% · 45th percentile
Show 75 more
  1. 2026-11-16 03:25 UTCEchelonGraph re-scored
  2. 2026-11-16 03:25 UTCVendor advisory
  3. 2026-11-16 03:25 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  4. 2026-11-15 16:58 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-11-15 02:08 UTCEchelonGraph re-scored
  6. 2026-11-15 02:08 UTCVendor advisory
  7. 2026-11-15 02:08 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  8. 2026-11-14 16:39 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  9. 2026-11-14 02:16 UTCEchelonGraph re-scored
  10. 2026-11-14 02:16 UTCVendor advisory
  11. 2026-11-14 02:16 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  12. 2026-11-13 16:51 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  13. 2026-11-13 02:24 UTCEchelonGraph re-scored
  14. 2026-11-13 02:24 UTCVendor advisory
  15. 2026-11-13 02:24 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  16. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-11-12 02:33 UTCEchelonGraph re-scored
  18. 2026-11-12 02:33 UTCVendor advisory
  19. 2026-11-12 02:33 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  20. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-11-11 02:42 UTCEchelonGraph re-scored
  22. 2026-11-11 02:42 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  23. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-11-10 13:28 UTCEchelonGraph re-scored
  25. 2026-11-10 13:28 UTCVendor advisory
  26. 2026-11-10 13:28 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  27. 2026-11-10 12:45 UTCEchelonGraph re-scored
  28. 2026-11-10 12:45 UTCVendor advisory
  29. 2026-11-10 12:45 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  30. 2026-11-09 17:27 UTCEchelonGraph re-scored
  31. 2026-11-09 17:27 UTCVendor advisory
  32. 2026-11-09 17:27 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  33. 2026-11-09 16:40 UTCEchelonGraph re-scored
  34. 2026-11-09 16:40 UTCVendor advisory
  35. 2026-11-09 16:40 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  36. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  37. 2026-11-08 17:40 UTCEchelonGraph re-scored
  38. 2026-11-08 17:40 UTCVendor advisory
  39. 2026-11-08 17:40 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  40. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  41. 2026-11-07 17:49 UTCEchelonGraph re-scored
  42. 2026-11-07 17:49 UTCVendor advisory
  43. 2026-11-07 17:49 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  44. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  45. 2026-11-06 17:58 UTCEchelonGraph re-scored
  46. 2026-11-06 17:58 UTCVendor advisory
  47. 2026-11-06 17:58 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  48. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  49. 2026-11-06 02:25 UTCOSV refresh
  50. 2026-11-05 18:07 UTCEchelonGraph re-scored
  51. 2026-11-05 18:07 UTCVendor advisory
  52. 2026-11-05 18:07 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  53. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  54. 2026-11-04 18:15 UTCEchelonGraph re-scored
  55. 2026-11-04 18:15 UTCVendor advisory
  56. 2026-11-04 18:15 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  57. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  58. 2026-11-03 18:24 UTCEchelonGraph re-scored
  59. 2026-11-03 18:24 UTCVendor advisory
  60. 2026-11-03 18:23 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  61. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  62. 2026-11-03 11:49 UTCEchelonGraph re-scored
  63. 2026-11-03 11:49 UTCVendor advisory
  64. 2026-11-03 11:49 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  65. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  66. 2026-11-02 11:58 UTCEchelonGraph re-scored
  67. 2026-11-02 11:58 UTCVendor advisory
  68. 2026-11-02 11:58 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  69. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  70. 2026-11-01 12:07 UTCEchelonGraph re-scored
  71. 2026-11-01 12:07 UTCVendor advisory
  72. 2026-11-01 12:07 UTCGHSA enrichmentGHSA-7jvw-f348-84gq · GitHub severity CRITICAL
  73. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  74. 2026-10-31 12:16 UTCEchelonGraph re-scored
  75. 2026-10-31 12:16 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-19445?
CVE-2026-19445 is a critical-severity vulnerability; its CVE record was published on September 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…
When was the CVE record for CVE-2026-19445 published?
The CVE record for CVE-2026-19445 was published on September 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-19445 actively exploited?
CVE-2026-19445 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19445?
CVE-2026-19445 has a CVSS base score of 9.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-19445?
A fix for CVE-2026-19445 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-19445 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-19445

Explore →

Is Your Infrastructure Affected by CVE-2026-19445?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.