{"id":"GHSA-xg4h-6gfc-h4m8","title":"etcd: Watch API authorization bypass via open-ended range requests","summary":"etcd: Watch API authorization bypass via open-ended range requests","severity":"high","cwe":["CWE-863"],"vendor":"etcd","product":"go.etcd.io/etcd/v3","ecosystem":"go","affected":["go.etcd.io/etcd/v3 >= 3.7.0-alpha.0, < 3.7.1","go.etcd.io/etcd/v3 >= 3.6.0, < 3.6.14","go.etcd.io/etcd/v3 < 3.5.33"],"patched":["go.etcd.io/etcd/v3 3.7.1","go.etcd.io/etcd/v3 3.6.14","go.etcd.io/etcd/v3 3.5.33"],"published":"2026-07-24","updated":"2026-07-24","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-xg4h-6gfc-h4m8","references":[{"url":"https://github.com/etcd-io/etcd/security/advisories/GHSA-xg4h-6gfc-h4m8"},{"url":"https://github.com/etcd-io/etcd/commit/6643f80602461a6095c9b294b6512fd9719bef41"},{"url":"https://github.com/etcd-io/etcd/commit/afeaa624da19085b47fb5ccc7c22a8c421bc2eae"},{"url":"https://github.com/etcd-io/etcd/commit/e863b001bbf3367003a543aa3099db9892134cd7"},{"url":"https://github.com/etcd-io/etcd/releases/tag/v3.5.33"},{"url":"https://github.com/etcd-io/etcd/releases/tag/v3.6.14"},{"url":"https://github.com/etcd-io/etcd/releases/tag/v3.7.1"},{"url":"https://github.com/advisories/GHSA-xg4h-6gfc-h4m8"}],"tags":["ghsa","go"],"ingestedAt":"2026-07-24T22:40:26.297Z","slug":"GHSA-xg4h-6gfc-h4m8","body":"## Overview\n\n### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nA user granted READ permission on a single, exact key can use the Watch gRPC API with `clientv3.WithFromKey()` (an open-ended, \"from this key to the end of the keyspace\" watch) to receive watch events for every key lexicographically greater than or equal to their permitted key — not just the one key they were granted. \n\nThis is an authorization bypass in etcd's RBAC enforcement for the Watch API; Range/Get and DeleteRange requests are not affected. It only affects clusters with authentication enabled — clusters running without auth already allow unrestricted read access.\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nThis vulnerability is patched in the following versions:\n\n- etcd 3.7.1\n- etcd 3.6.14\n- etcd 3.5.33\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nIf upgrading is not immediately possible, the following mitigations reduce exposure:\n\n- Audit READ grants. Any READ grant — even on one key — can be leveraged via Watch to read everything after it. Review who holds READ permissions and revoke/tighten any you wouldn't trust with full read access.\n- Restrict network access. Limit which hosts can reach etcd's client (gRPC) port via firewall rules or network policy, reducing who can attempt exploitation.\n\n### Reporter\n\n- Luis Toro ([@lobuhi](https://github.com/lobuhi) on Github)\n- Anthropic  and Adam Korczynski ([@AdamKorcz](https://github.com/AdamKorcz) on Github)\n\n## Affected packages\n\n- `go.etcd.io/etcd/v3 >= 3.7.0-alpha.0, < 3.7.1`\n- `go.etcd.io/etcd/v3 >= 3.6.0, < 3.6.14`\n- `go.etcd.io/etcd/v3 < 3.5.33`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `go.etcd.io/etcd/v3 3.7.1`\n- `go.etcd.io/etcd/v3 3.6.14`\n- `go.etcd.io/etcd/v3 3.5.33`","depth":"twilight","depthScore":41,"depthScoreParts":{"impact":41.3,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}