CVE-2023-40217

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2023-08-25. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

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.)

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

August 25, 2023

Last Modified

November 3, 2025

References (12)

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)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.5-venv (3.5.2-2ubuntu0~16.04.13+esm12) @ xenial2026-05-23ubuntu
ubuntupython2.7-minimal (2.7.18-13ubuntu1.5) @ jammy2026-05-23ubuntu
ubuntupython3.8-venv (3.8.0-3ubuntu1~18.04.2+esm2) @ bionic2026-05-23ubuntu
ubuntupython3.11-venv (3.11.4-1~23.04.1) @ lunar2026-05-23ubuntu
redhatpython-0:2.7.5-94.el7_92023-11-13redhat
redhatpython3-0:3.6.8-21.el7_92023-11-08redhat
redhatrh-python38-python-0:3.8.18-2.el72023-11-08redhat
redhatpython-0:2.6.6-70.el6_102023-11-02redhat
redhatpython39:3.9-8040020230922214438.63cd9eba2023-10-24redhat
redhatpython39-devel:3.9-8060020230922214243.6a6313992023-10-24redhat
redhatpython27:2.7-8040020231004234308.7c6da4642023-10-23redhat
redhatpython3-0:3.6.8-51.el8_8.22023-10-23redhat
redhatpython3-0:3.6.8-15.1.el8_1.22023-10-23redhat
redhatpython27:2.7-8080020231004233750.392b0bf12023-10-23redhat
redhatpython39-devel:3.9-8080020230922214114.93c2fc2f2023-10-23redhat
redhatpython27:2.7-8010020231004234533.208b345f2023-10-23redhat
redhatpython27:2.7-8020020231004234409.c9f5743f2023-10-23redhat
redhatpython3-0:3.6.8-39.el8_4.32023-10-23redhat
redhatpython27:2.7-8060020231004234102.2aa69ce42023-10-23redhat
redhatpython3-0:3.6.8-47.el8_6.22023-10-09redhat
redhatpython3-0:3.6.8-24.el8_2.22023-10-09redhat
redhatpython3.9-0:3.9.16-1.el9_2.22023-10-05redhat
redhatpython3.9-0:3.9.10-4.el9_0.22023-10-05redhat
redhatpython3.11-0:3.11.2-2.el9_2.22023-10-05redhat
redhatpython3.11-0:3.11.2-2.el8_8.22023-10-05redhat

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.

Affected Packages

(19 across 15 ecosystems)
Debian:11(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.5+dfsg-2, 7.3.5+dfsg-2+deb11u1, 7.3.5+dfsg-2+deb11u27.3.5+dfsg-2+deb11u3—
python2.72.7.18-82.7.18-8+deb11u1—
python3.93.9.2-1, 3.9.2-1+deb11u13.9.2-1+deb11u2—
Debian:10(2)
PackageVulnerable rangeFixed inDependents
python2.72.7.16-2, 2.7.16-2+deb10u1, 2.7.16-2+deb10u22.7.16-2+deb10u3—
python3.73.7.3-2 ... 3.7.3-2+deb10u5 (6 versions)3.7.3-2+deb10u6—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.11+dfsg-2, 7.3.11+dfsg-2+deb12u17.3.11+dfsg-2+deb12u2—
python3.113.11.2-6, 3.11.2-6+deb12u13.11.2-6+deb12u2—
Alpine:v3.15(1)
PackageVulnerable rangeFixed inDependents
python3—3.9.18-r0—
Alpine:v3.16(1)
PackageVulnerable rangeFixed inDependents
python3—3.10.13-r0—
Alpine:v3.17(1)
PackageVulnerable rangeFixed inDependents
python3—3.10.13-r0—
Alpine:v3.18(1)
PackageVulnerable rangeFixed inDependents
python3—3.11.5-r0—
Alpine:v3.19(1)
PackageVulnerable rangeFixed inDependents
python3—3.11.5-r0—
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
python3—3.11.5-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
python3—3.11.5-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
python3—3.11.5-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
python3—3.11.5-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
python3—3.11.5-r0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pypy3—7.3.13+dfsg-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pypy3—7.3.13+dfsg-1—

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.

Data Freshness Timeline

(refreshed 7× 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 135 total refreshes for this CVE.

  1. 2026-08-09 13:44 UTCEPSS rescore
  2. 2026-08-09 13:44 UTCEPSS rescore
  3. 2026-08-08 16:35 UTCEPSS rescore
  4. 2026-08-07 16:25 UTCEPSS rescore
  5. 2026-08-06 13:45 UTCEPSS rescore
  6. 2026-08-05 19:15 UTCEPSS rescore
  7. 2026-08-04 15:07 UTCEPSS rescore
  8. 2026-08-03 10:34 UTCEPSS rescore
  9. 2026-08-03 10:34 UTCEPSS rescore
  10. 2026-08-02 02:25 UTCEPSS rescore
  11. 2026-08-02 02:25 UTCEPSS rescore
  12. 2026-08-01 04:14 UTCEPSS rescore
  13. 2026-08-01 04:13 UTCEPSS rescore
  14. 2026-07-30 20:51 UTCOSV refresh
  15. 2026-07-30 16:26 UTCEPSS rescore
  16. 2026-07-30 16:26 UTCEPSS rescore
  17. 2026-07-30 01:28 UTCEPSS rescore
  18. 2026-07-30 01:28 UTCEPSS rescore
  19. 2026-07-28 15:34 UTCEPSS rescore
  20. 2026-07-28 15:34 UTCEPSS rescore
  21. 2026-07-26 14:52 UTCEPSS rescore
  22. 2026-07-26 14:52 UTCEPSS rescore
  23. 2026-07-25 14:16 UTCEPSS rescore
  24. 2026-07-24 14:16 UTCEPSS rescore
  25. 2026-07-23 14:16 UTCEPSS rescore
Show 75 more
  1. 2026-07-23 14:16 UTCEPSS rescore
  2. 2026-07-23 02:25 UTCEG score recompute
  3. 2026-07-22 23:12 UTCEG score recompute
  4. 2026-07-22 14:06 UTCEPSS rescore
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-21 15:23 UTCEPSS rescore
  7. 2026-07-20 17:06 UTCEPSS rescore
  8. 2026-07-19 14:29 UTCEPSS rescore
  9. 2026-07-19 02:27 UTCEPSS rescore
  10. 2026-07-18 10:03 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-16 17:01 UTCEPSS rescore
  13. 2026-07-16 17:01 UTCEPSS rescore
  14. 2026-07-15 16:56 UTCEPSS rescore
  15. 2026-07-15 16:56 UTCEPSS rescore
  16. 2026-07-15 01:58 UTCEPSS rescore
  17. 2026-07-13 22:28 UTCEPSS rescore
  18. 2026-07-13 22:28 UTCEPSS rescore
  19. 2026-07-13 06:11 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-13 06:07 UTCOSV refresh
  22. 2026-07-12 05:45 UTCEPSS rescore
  23. 2026-07-12 05:45 UTCEPSS rescore
  24. 2026-07-11 08:26 UTCEPSS rescore
  25. 2026-07-11 08:26 UTCEPSS rescore
  26. 2026-07-09 19:08 UTCEPSS rescore
  27. 2026-07-08 15:13 UTCEPSS rescore
  28. 2026-07-07 13:44 UTCEPSS rescore
  29. 2026-07-06 16:26 UTCEPSS rescore
  30. 2026-07-06 16:26 UTCEPSS rescore
  31. 2026-07-06 02:22 UTCEPSS rescore
  32. 2026-07-05 02:29 UTCEPSS rescore
  33. 2026-07-04 06:29 UTCEPSS rescore
  34. 2026-07-01 15:05 UTCEPSS rescore
  35. 2026-06-30 23:21 UTCEPSS rescore
  36. 2026-06-30 23:21 UTCEPSS rescore
  37. 2026-06-28 14:06 UTCEPSS rescore
  38. 2026-06-28 14:06 UTCEPSS rescore
  39. 2026-06-28 04:55 UTCEPSS rescore
  40. 2026-06-28 04:55 UTCEPSS rescore
  41. 2026-06-27 03:07 UTCEPSS rescore
  42. 2026-06-27 03:07 UTCEPSS rescore
  43. 2026-06-25 13:48 UTCEPSS rescore
  44. 2026-06-25 13:48 UTCEPSS rescore
  45. 2026-06-24 18:01 UTCOSV refresh
  46. 2026-06-24 14:04 UTCEPSS rescore
  47. 2026-06-24 14:04 UTCEPSS rescore
  48. 2026-06-23 21:31 UTCEPSS rescore
  49. 2026-06-23 21:31 UTCEPSS rescore
  50. 2026-06-22 14:24 UTCEPSS rescore
  51. 2026-06-22 14:24 UTCEPSS rescore
  52. 2026-06-21 14:55 UTCEPSS rescore
  53. 2026-06-21 14:55 UTCEPSS rescore
  54. 2026-06-21 01:58 UTCEPSS rescore
  55. 2026-06-21 01:58 UTCEPSS rescore
  56. 2026-06-19 19:24 UTCEPSS rescore
  57. 2026-06-19 19:24 UTCEPSS rescore
  58. 2026-06-18 17:51 UTCEPSS rescore
  59. 2026-06-17 17:51 UTCEPSS rescore
  60. 2026-06-17 17:51 UTCEPSS rescore
  61. 2026-06-16 17:51 UTCEPSS rescore
  62. 2026-06-16 17:51 UTCEPSS rescore
  63. 2026-06-15 17:47 UTCEPSS rescore
  64. 2026-06-15 17:47 UTCEPSS rescore
  65. 2026-06-14 23:16 UTCEPSS rescore
  66. 2026-06-13 22:59 UTCEPSS rescore
  67. 2026-06-13 22:59 UTCEPSS rescore
  68. 2026-06-12 23:10 UTCEPSS rescore
  69. 2026-06-12 23:10 UTCEPSS rescore
  70. 2026-06-11 13:59 UTCEPSS rescore
  71. 2026-06-11 13:59 UTCEPSS rescore
  72. 2026-06-10 22:17 UTCEPSS rescore
  73. 2026-06-10 13:21 UTCEPSS rescore
  74. 2026-06-10 13:21 UTCEPSS rescore
  75. 2026-06-08 14:16 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2023-40217?
CVE-2023-40217 is a medium vulnerability published on August 25, 2023. 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…
When was CVE-2023-40217 disclosed?
CVE-2023-40217 was first published in the National Vulnerability Database on August 25, 2023, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-40217 actively exploited?
CVE-2023-40217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 47.1% of all scored CVEs.
What is the CVSS score of CVE-2023-40217?
CVE-2023-40217 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2023-40217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-40217, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-40217

Explore →

Is Your Infrastructure Affected by CVE-2023-40217?

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

Start Free Scan →Browse All CVEs