Skip to main content
VulnerabilityPublished 07/25/2026

V3: etcd: Watch API authorization bypass via open-ended range requests

Affects go.etcd.io/etcd/v3Source GCVE Database

0

Fixed in 3.7.1 : patch go.etcd.io/etcd/v3 soon.

Data as of 08/18/2026, 13:43:13 UTC

Severity
High

Rated by Threat Radar

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:N

What to do

Affected software

ProductAffectedFixed in
Gogo.etcd.io/etcd/v3Affected
  • >=3.7.0-alpha.0 <3.7.1
Fixed in
  • 3.7.1
Gogo.etcd.io/etcd/v3Affected
  • >=3.6.0 <3.6.14
Fixed in
  • 3.6.14
Gogo.etcd.io/etcd/v3Affected
  • <3.5.33
Fixed in
  • 3.5.33

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade etcd to version 3.5.33, 3.6.14, or 3.7.1 or later, where this authorization bypass issue is fixed. Since a patch is available, applying the official fix is the recommended remediation. No other mitigations are indicated or necessary for this specific vulnerability.

Description

A vulnerability in etcd's Watch API allows a user with READ permission on a single exact key to bypass authorization and watch events for all keys lexicographically greater than or equal to that key. This affects versions prior to 3.5.33, 3.6.14, and 3.7.1 when authentication is enabled. The issue arises because the open-ended RangeEnd sentinel is rewritten before the RBAC permission check, causing improper permission validation. This flaw does not affect Range/Get or DeleteRange requests and only impacts clusters with authentication enabled. The vulnerability has been fixed in the specified versions.

Impact

An attacker with READ permission on a single exact key can bypass intended authorization restrictions and observe watch events for a broader set of keys, potentially exposing more data than permitted. This could lead to unauthorized data disclosure within the etcd key-value store. The impact is limited to clusters with authentication enabled and does not affect other request types like Range/Get or DeleteRange.

Weaknesses

  • CWE-863Incorrect Authorization (opens in a new tab)

    Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)

    The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

References

Community reviews

Loading reviews…