An issue was discovered in Python before 3.8.18, 3.9.x before 3.9.18, 3.10.x before 3.10.13, and 3.11.x before 3.11.5. It primarily affects servers (such as HTTP servers) that use TLS client authentication. If a TLS server-side socket is created, receives data into the socket buffer, and then is closed quickly, there is a brief window where the SSLSocket instance will detect the socket as "not connected" and won't initiate a handshake, but buffered data will still be readable from the socket buffer. This data will not be authenticated if the server-side TLS peer is expecting client certificate authentication, and is indistinguishable from valid TLS stream data. Data is limited in size to the amount that will fit in the buffer. (The TLS connection cannot directly be used for data exfiltration because the vulnerable code path requires that the connection be closed on initialization of the SSLSocket.)
CVE-2023-40217
Score 5.3 from GitHub Security Advisory published 2023-08-25. NVD baseline CVSS 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EPSS
- 52.4%
- KEV
- Not listed
Published
August 25, 2023
Last Modified
November 3, 2025
References (12)
- cve@mitrehttps://lists.debian.org/debian-lts-announce/2023/09/msg00022.html
- cve@mitrehttps://lists.debian.org/debian-lts-announce/2023/10/msg00017.html
- cve@mitrehttps://mail.python.org/archives/list/security-announce%40python.org/thread/PEPLII27KYHLF4AK3ZQGKYNCRERG4YXY/
- cve@mitrehttps://security.netapp.com/advisory/ntap-20231006-0014/
- cve@mitrehttps://www.python.org/dev/security/
- af854a3a-2127-422b-91ae-364da2661108https://lists.debian.org/debian-lts-announce/2023/09/msg00022.html
- af854a3a-2127-422b-91ae-364da2661108https://lists.debian.org/debian-lts-announce/2023/10/msg00017.html
- af854a3a-2127-422b-91ae-364da2661108https://lists.debian.org/debian-lts-announce/2024/11/msg00005.html
- af854a3a-2127-422b-91ae-364da2661108https://lists.debian.org/debian-lts-announce/2024/12/msg00000.html
- af854a3a-2127-422b-91ae-364da2661108https://mail.python.org/archives/list/security-announce%40python.org/thread/PEPLII27KYHLF4AK3ZQGKYNCRERG4YXY/
- af854a3a-2127-422b-91ae-364da2661108https://security.netapp.com/advisory/ntap-20231006-0014/
- af854a3a-2127-422b-91ae-364da2661108https://www.python.org/dev/security/
Vendor Advisories for CVE-2023-40217(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(25)
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Additional Vendor Advisories
(24)
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.
- Microsoft MSRCCVE-2023-402172023-10-11
An issue was discovered in Python before 3.8.18 3.9.x before 3.9.18 3.10.x before 3.10.13 and 3.11.x before 3.11.5. It primarily affects servers (such as HTTP servers) that use TLS client authentication. If a TLS server-side socket is created receives data into the socket buffer and then is closed quickly there is a brief window where the SSLSocket instance will detect the socket as "not connected" and won't initiate a handshake but buffered data will still be readable from the socket buffer. This data will not be authenticated if the server-side TLS peer is expecting client certificate authentication and is indistinguishable from valid TLS stream data. Data is limited in size to the amount that will fit in the buffer. (The TLS connection cannot directly be used for data exfiltration because the vulnerable code path requires that the connection be closed on initialization of the SSLSocket.)
- Red HatRHSA-2023:5456IMPORTANT2023-08-25
RHSA-2023:5456 — Important
- Red HatRHSA-2023:5462IMPORTANT2023-08-25
RHSA-2023:5462 — Important
- Red HatRHSA-2023:5463IMPORTANT2023-08-25
RHSA-2023:5463 — Important
- Red HatRHSA-2023:5472IMPORTANT2023-08-25
RHSA-2023:5472 — Important
- Red HatRHSA-2023:5528IMPORTANT2023-08-25
RHSA-2023:5528 — Important
- Red HatRHSA-2023:5531IMPORTANT2023-08-25
RHSA-2023:5531 — Important
- Red HatRHSA-2023:5990IMPORTANT2023-08-25
RHSA-2023:5990 — Important
- Red HatRHSA-2023:5991IMPORTANT2023-08-25
RHSA-2023:5991 — Important
- Red HatRHSA-2023:5992IMPORTANT2023-08-25
RHSA-2023:5992 — Important
- Red HatRHSA-2023:5993IMPORTANT2023-08-25
RHSA-2023:5993 — Important
- Red HatRHSA-2023:5994IMPORTANT2023-08-25
RHSA-2023:5994 — Important
- Red HatRHSA-2023:5995IMPORTANT2023-08-25
RHSA-2023:5995 — Important
- Red HatRHSA-2023:5996IMPORTANT2023-08-25
RHSA-2023:5996 — Important
- Red HatRHSA-2023:5997IMPORTANT2023-08-25
RHSA-2023:5997 — Important
- Red HatRHSA-2023:5998IMPORTANT2023-08-25
RHSA-2023:5998 — Important
- Red HatRHSA-2023:6068IMPORTANT2023-08-25
RHSA-2023:6068 — Important
- Red HatRHSA-2023:6069IMPORTANT2023-08-25
RHSA-2023:6069 — Important
- Red HatRHSA-2023:6290IMPORTANT2023-08-25
RHSA-2023:6290 — Important
- Red HatRHSA-2023:6823IMPORTANT2023-08-25
RHSA-2023:6823 — Important
- Red HatRHSA-2023:6885IMPORTANT2023-08-25
RHSA-2023:6885 — Important
- UbuntuUSN-6513-1MEDIUM
Python vulnerabilities
- UbuntuUSN-6513-2MEDIUM
Python vulnerability
- UbuntuUSN-6891-1MEDIUM
Python vulnerabilities
Data Freshness Timeline
(refreshed 10× in last 7d / 46× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 107 total refreshes for this CVE.
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-20 17:06 UTCEPSS rescore
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-16 17:01 UTCEPSS rescore
- 2026-07-16 17:01 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-13 06:11 UTCEPSS rescore
- 2026-07-13 06:07 UTCOSV refresh
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-12 05:45 UTCEPSS rescore
- 2026-07-11 08:26 UTCEPSS rescore
- 2026-07-11 08:26 UTCEPSS rescore
- 2026-07-09 19:08 UTCEPSS rescore
- 2026-07-08 15:13 UTCEPSS rescore
- 2026-07-07 13:44 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-06 16:26 UTCEPSS rescore
- 2026-07-06 16:26 UTCEPSS rescore
- 2026-07-06 02:22 UTCEPSS rescore
- 2026-07-05 02:29 UTCEPSS rescore
- 2026-07-04 06:29 UTCEPSS rescore
- 2026-07-01 15:05 UTCEPSS rescore
- 2026-06-30 23:21 UTCEPSS rescore
- 2026-06-30 23:21 UTCEPSS rescore
- 2026-06-28 14:06 UTCEPSS rescore
- 2026-06-28 14:06 UTCEPSS rescore
- 2026-06-28 04:55 UTCEPSS rescore
- 2026-06-28 04:55 UTCEPSS rescore
- 2026-06-27 03:07 UTCEPSS rescore
- 2026-06-27 03:07 UTCEPSS rescore
- 2026-06-25 13:48 UTCEPSS rescore
- 2026-06-25 13:48 UTCEPSS rescore
- 2026-06-24 18:01 UTCOSV refresh
- 2026-06-24 14:04 UTCEPSS rescore
- 2026-06-24 14:04 UTCEPSS rescore
- 2026-06-23 21:31 UTCEPSS rescore
- 2026-06-23 21:31 UTCEPSS rescore
- 2026-06-22 14:24 UTCEPSS rescore
- 2026-06-22 14:24 UTCEPSS rescore
- 2026-06-21 14:55 UTCEPSS rescore
- 2026-06-21 14:55 UTCEPSS rescore
- 2026-06-21 01:58 UTCEPSS rescore
- 2026-06-21 01:58 UTCEPSS rescore
- 2026-06-19 19:24 UTCEPSS rescore
- 2026-06-19 19:24 UTCEPSS rescore
- 2026-06-18 17:51 UTCEPSS rescore
- 2026-06-17 17:51 UTCEPSS rescore
- 2026-06-17 17:51 UTCEPSS rescore
- 2026-06-16 17:51 UTCEPSS rescore
- 2026-06-16 17:51 UTCEPSS rescore
- 2026-06-15 17:47 UTCEPSS rescore
- 2026-06-15 17:47 UTCEPSS rescore
- 2026-06-14 23:16 UTCEPSS rescore
- 2026-06-13 22:59 UTCEPSS rescore
- 2026-06-13 22:59 UTCEPSS rescore
- 2026-06-12 23:10 UTCEPSS rescore
- 2026-06-12 23:10 UTCEPSS rescore
- 2026-06-11 13:59 UTCEPSS rescore
- 2026-06-11 13:59 UTCEPSS rescore
- 2026-06-10 22:17 UTCEPSS rescore
- 2026-06-10 13:21 UTCEPSS rescore
- 2026-06-10 13:21 UTCEPSS rescore
- 2026-06-08 14:16 UTCEPSS rescore
- 2026-06-08 14:16 UTCEPSS rescore
- 2026-06-07 19:46 UTCOSV refresh
- 2026-06-07 15:23 UTCEPSS rescore
- 2026-06-07 15:23 UTCEPSS rescore
- 2026-06-06 13:46 UTCEPSS rescore
- 2026-06-06 13:46 UTCEPSS rescore
- 2026-06-05 22:46 UTCEPSS rescore
- 2026-06-05 22:46 UTCEPSS rescore
- 2026-06-05 06:09 UTCEPSS rescore
- 2026-06-05 06:09 UTCEPSS rescore
- 2026-06-05 06:09 UTCEPSS rescore
- 2026-06-04 13:11 UTCEPSS rescore
- 2026-06-04 13:11 UTCEPSS rescore
- 2026-06-02 20:12 UTCEPSS rescore
- 2026-06-02 20:12 UTCEPSS rescore
- 2026-06-01 13:51 UTCEPSS rescore
- 2026-06-01 13:51 UTCEPSS rescore
- 2026-05-31 22:30 UTCEPSS rescore
- 2026-05-31 22:29 UTCEPSS rescore
- 2026-05-31 00:15 UTCEPSS rescore
- 2026-05-31 00:15 UTCEPSS rescore
- 2026-05-29 13:43 UTCEPSS rescore
- 2026-05-29 13:43 UTCEPSS rescore
- 2026-05-28 13:44 UTCEPSS rescore
- 2026-05-28 13:43 UTCEPSS rescore
- 2026-05-27 13:39 UTCEPSS rescore
- 2026-05-27 13:39 UTCEPSS rescore
- 2026-05-26 13:43 UTCEPSS rescore
Frequently asked(5)
What is CVE-2023-40217?
When was CVE-2023-40217 disclosed?
Is CVE-2023-40217 actively exploited?
What is the CVSS score of CVE-2023-40217?
How do I remediate CVE-2023-40217?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2023-40217
Is Your Infrastructure Affected by CVE-2023-40217?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.