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.4%, top 71% of all CVEs by exploit prediction. 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%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.1(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 14, 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 Patch Available

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(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
go.etcd.io/etcd/v3—3.7.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 33× 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-08-26 14:47 UTCEPSS rescore
  2. 2026-08-26 01:35 UTCEG score recompute
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-25 00:41 UTCEG score recompute
  5. 2026-08-24 12:12 UTCEG score recompute
  6. 2026-08-23 11:20 UTCEG score recompute
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 10:28 UTCEG score recompute
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-21 09:35 UTCEG score recompute
  11. 2026-08-20 22:56 UTCEPSS rescore
  12. 2026-08-19 20:17 UTCEG score recompute
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-18 18:51 UTCEG score recompute
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 13:49 UTCEPSS rescore
  17. 2026-08-18 01:56 UTCEG score recompute
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 01:04 UTCEG score recompute
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 12:38 UTCEG score recompute
  23. 2026-08-16 02:15 UTCEPSS rescore
  24. 2026-08-15 11:46 UTCEG score recompute
  25. 2026-08-15 01:31 UTCEPSS rescore
Show 8 more
  1. 2026-08-14 23:19 UTCEG score recompute
  2. 2026-08-14 22:24 UTCEG score recompute
  3. 2026-08-13 23:13 UTCEG score recompute
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-12 22:21 UTCEG score recompute
  6. 2026-08-12 21:41 UTCEG score recompute▲ 7.10
  7. 2026-08-12 21:40 UTCMITRE cvelistV5CVSS v3 → 7.1 · CVSS v4 → 7.1
  8. 2026-08-12 21:21 UTCEG score recompute

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 in the National Vulnerability Database on July 24, 2026, with the most recent update on August 14, 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% probability of exploitation in the next 30 days, which ranks it in the top 70.7% of all scored CVEs.
What is the CVSS score of CVE-2026-73499?
CVE-2026-73499 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-73499?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73499, 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-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.

Start Free Scan →Browse All CVEs