CVE-2026-73499: etcd · Incorrect Authorization
Affects etcdSource CVE Database V5
Not known to be exploited · CVSS 7.1 High · fixed in 3.7.1 : patch etcd soon.
Data as of 9 Nov 2026, 23:24 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.7.1, 3.6.14, 3.5.33
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade etcd and etcd-io/etcd to 3.7.1, 3.6.14 or 3.5.33.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| etcd-ioetcd | Affected
| Fixed in
|
| etcd-ioetcd | Affected
| Fixed in
|
| etcd-ioetcd | Affected
| Fixed in
|
GitHubetcd-io/etcdpkg:github/etcd-io/etcdOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in etcd versions 3.5.33, 3.6.14, and 3.7.1. Users should upgrade to these or later versions to remediate the issue. No other mitigation or temporary workaround is indicated. Since this is not a cloud service, remediation depends on user action to upgrade.
Description
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.
References
- github.com/etcd-io/etcd/security/advisories/GHSA-xg4h-6gfc-h4m8 (opens in a new tab)
- github.com/etcd-io/etcd/commit/6643f80602461a6095c9b294b6512fd9719bef41 (opens in a new tab)
- github.com/etcd-io/etcd/commit/7cf71ec9e2ec54230a5454392fa4ffd4574b41ed (opens in a new tab)
- github.com/etcd-io/etcd/commit/afeaa624da19085b47fb5ccc7c22a8c421bc2eae (opens in a new tab)
- github.com/etcd-io/etcd/commit/e863b001bbf3367003a543aa3099db9892134cd7 (opens in a new tab)
- github.com/etcd-io/etcd/releases/tag/v3.5.33 (opens in a new tab)
- github.com/etcd-io/etcd/releases/tag/v3.6.14 (opens in a new tab)
- github.com/etcd-io/etcd/releases/tag/v3.7.1 (opens in a new tab)