CVE-2026-73500

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.5.33, 3.6.14, and 3.7.1, a network attacker who can reach an etcd TLS listener can open many TCP connections and never send a ClientHello. In client/pkg/transport/listener_tls.go, each connection handled by tlsListener.acceptLoop spawns a goroutine that blocks indefinitely inside tls.Conn.Handshake() and remains tracked in the pending map. Unbounded goroutine and map growth can exhaust memory in the etcd process, causing loss of availability for the cluster and, when etcd backs Kubernetes, the control plane. This issue is fixed in versions 3.5.33, 3.6.14, and 3.7.1.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
54
EG Risk 54/100CISA SSVC

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
Severity87% × 45%
Exploitation1% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 12, 2026

Last Modified

September 18, 2026

Advisory Details (9)

Auto-updated Aug 12, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

v3.7.1

Patch available: etcd-io/etcd v3.7.1

https://github.com/etcd-io/etcd/releases/tag/v3.7.1
github_release Patch Available

v3.6.14

Patch available: etcd-io/etcd v3.6.14

https://github.com/etcd-io/etcd/releases/tag/v3.6.14
github_release Patch Available

v3.5.33

Patch available: etcd-io/etcd v3.5.33

https://github.com/etcd-io/etcd/releases/tag/v3.5.33
github_commit

commit f73cba7d9200 (etcd-io/etcd)

Fix landed in etcd-io/etcd commit f73cba7d9200 — awaiting tagged release

https://github.com/etcd-io/etcd/commit/f73cba7d920019f91a1ea1f6697833e42731f057
github_commit

commit 8e4dd0679a2c (etcd-io/etcd)

Fix landed in etcd-io/etcd commit 8e4dd0679a2c — awaiting tagged release

https://github.com/etcd-io/etcd/commit/8e4dd0679a2c6b095d2a32a749fda2521c7809a3
github_commit

commit 89ff6d507960 (etcd-io/etcd)

Fix landed in etcd-io/etcd commit 89ff6d507960 — awaiting tagged release

https://github.com/etcd-io/etcd/commit/89ff6d50796049d4f1136915ba21504b76e7e372
github_commit

commit 2e07efce9745 (etcd-io/etcd)

Fix landed in etcd-io/etcd commit 2e07efce9745 — awaiting tagged release

https://github.com/etcd-io/etcd/commit/2e07efce9745004eb4773cffaada9b5cdf77cff2
github_pr

Set a tlsHandshakeTimeout for tlsListener

Fix merged in etcd-io/etcd PR #22130 on 2026-07-21 — awaiting tagged release

https://github.com/etcd-io/etcd/pull/22130
githubMentions a patch (unverified)

`tlsListener.acceptLoop` spawns unbounded handshake goroutines with no deadline · Advisory · etcd-io/etcd · GitHub

https://github.com/etcd-io/etcd/security/advisories/GHSA-6vch-q96h-7gc3

Patch Availability(13)

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

(5 across 4 ecosystems)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
go.etcd.io/etcd/client/pkg/v3—
  • every version up to 3.5.33: fixed in 3.5.33
  • 3.6.0 up to 3.6.14: fixed in 3.6.14
  • 3.7.0-alpha.0 up to 3.7.1: fixed in 3.7.1
—
go.etcd.io/etcd/v3—
  • 3.7.0-alpha.0 up to 3.7.1: fixed in 3.7.1
  • 3.6.0 up to 3.6.14: fixed in 3.6.14
  • every version up to 3.5.33: fixed in 3.5.33
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
etcd3.4.23-4 ... 3.5.5-1 (30 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
etcd3.5.16-10 ... 3.5.30-2 (13 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
etcd3.5.16-10 ... 3.5.30-2 (13 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 87× 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 177 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-73500?
CVE-2026-73500 is a high vulnerability published on August 12, 2026. etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.5.33, 3.6.14, and 3.7.1, a network attacker who can reach an etcd TLS listener can open many TCP connections and never send a ClientHello. In client/pkg/transport/listener_tls.go, each connection handled…
When was CVE-2026-73500 disclosed?
CVE-2026-73500 was first published on August 12, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73500 actively exploited?
CVE-2026-73500 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73500?
CVE-2026-73500 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73500?
A fix for CVE-2026-73500 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73500 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-73500

Explore →

Is Your Infrastructure Affected by CVE-2026-73500?

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