CVE-2026-73499

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (51st 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 — 3 sources updated this week

Also known asEUVD-2026-57641 (ENISA EUVD) · GHSA-xg4h-6gfc-h4m8 (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
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: 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/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
51st
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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 every mission impact level.CISA BOD 26-04: 60 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 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). 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)60 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 partial (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

July 24, 2026

Last Modified

October 24, 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
GitHub advisoryMentions 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.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogo.etcd.io/etcd/v3 @ 3.7.1 (fixes >= 3.7.0-alpha.0, < 3.7.1)—ghsa
gogo.etcd.io/etcd/v3 @ 3.6.14 (fixes >= 3.6.0, < 3.6.14)—ghsa
gogo.etcd.io/etcd/v3 @ 3.5.33 (fixes < 3.5.33)—ghsa

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/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 10× in last 7d / 43× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 98 of 128 refreshes 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 30 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-73499?
CVE-2026-73499 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-73499 published?
The CVE record for CVE-2026-73499 was published on July 24, 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 October 24, 2026; the record at its source may have been updated since.
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 (51st 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