CVE-2026-73499

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (49th 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
7.1EG
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: 7.1Exploit: 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 user granted READ permission on a single exact key can use the Watch gRPC API with clientv3.WithFromKey() to receive watch events for every key lexicographically greater than or equal to the permitted key. In server/etcdserver/api/v3rpc/watch.go, the open-ended RangeEnd sentinel is rewritten before the RBAC permission check in server/auth/range_perm_cache.go function isRangeOpPermitted, causing the request to be treated as an exact-key watch. Range/Get and DeleteRange requests are not affected, and the issue affects only clusters with authentication enabled. This issue is fixed in versions 3.5.33, 3.6.14, and 3.7.1.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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
Severity71% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (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

July 24, 2026

Last Modified

September 18, 2026

Advisory Details (8)

Auto-updated Aug 12, 2026
Patch available. Sources: github, 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 e863b001bbf3 (etcd-io/etcd)

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

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

commit afeaa624da19 (etcd-io/etcd)

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

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

commit 7cf71ec9e2ec (etcd-io/etcd)

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

https://github.com/etcd-io/etcd/commit/7cf71ec9e2ec54230a5454392fa4ffd4574b41ed
github_commit

commit 6643f8060246 (etcd-io/etcd)

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

https://github.com/etcd-io/etcd/commit/6643f80602461a6095c9b294b6512fd9719bef41
githubMentions a patch (unverified)

Watch API authorization bypass via open-ended range requests · Advisory · etcd-io/etcd · GitHub

https://github.com/etcd-io/etcd/security/advisories/GHSA-xg4h-6gfc-h4m8

Vendor Advisories for CVE-2026-73499(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 4 ecosystems)
Go(2)
PackageVulnerable rangeFix by version rangeDependents
go.etcd.io/etcd/server/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 8× in last 7d / 38× 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.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-73499?
CVE-2026-73499 is a high vulnerability published on July 24, 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 user granted READ permission on a single exact key can use the Watch gRPC API with clientv3.WithFromKey() to receive watch events for every key lexicographically greater than…
When was CVE-2026-73499 disclosed?
CVE-2026-73499 was first published on July 24, 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-73499 actively exploited?
CVE-2026-73499 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73499?
CVE-2026-73499 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-73499?
A fix for CVE-2026-73499 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73499 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-73499

Explore →

Is Your Infrastructure Affected by CVE-2026-73499?

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

Book a Demo →Browse All CVEs