CVE-2026-44283: etcd RBAC bypass allows unauthorized data access via PrevKv/lease attachment in nested transaction Put requests
Impact What kind of vulnerability is it? Who is impacted? A vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user without sufficient read or lease-related permissions may be able to access unauthorized data or attach leases by invoking transaction operations with these features enabled.
Published May 7, 2026 · Updated May 14, 2026
Affected packages
go.etcd.io/etcd/v3
- Ecosystem
- Go
- Affected
- >= 3.6.0, <= 3.6.10
- Fixed in
- 3.6.11
- Check
go list -m go.etcd.io/etcd/v3
go.etcd.io/etcd/v3
- Ecosystem
- Go
- Affected
- >= 3.5.0, <= 3.5.29
- Fixed in
- 3.5.30
- Check
go list -m go.etcd.io/etcd/v3
go.etcd.io/etcd
- Ecosystem
- Go
- Affected
- <= 3.4.43
- Fixed in
- 3.4.44
- Check
go list -m go.etcd.io/etcd
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
_What kind of vulnerability is it? Who is impacted?_
A vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user without sufficient read or lease-related permissions may be able to access unauthorized data or attach leases by invoking transaction operations with these features enabled.
Kubernetes does not rely on etcd’s built-in authentication and authorization. Instead, the API server handles authentication and authorization itself, so typical Kubernetes deployments are not affected.
Patches
_Has the problem been patched? What versions should users upgrade to?_
This vulnerability is patched in the following versions:
- etcd 3.6.11
- etcd 3.5.30
- etcd 3.4.44
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
If upgrading is not immediately possible, reduce exposure by treating the affected RPCs as unauthenticated in practice.
- restrict network access to etcd server ports so only trusted components can connect
- require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate
distribution
Reporters
Samy Ghannad (@SamyGhannad on Github) reported that read access via PrevKv in a Put request within etcd transactions bypassed RBAC authorization checks. Benjamin Wang (@ahrtr ) further analyzed that lease attachment in a Put request within etcd transactions also bypassed RBAC authorization checks
Credited to SamyGhannad.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-73499
etcd: Watch API authorization bypass via open-ended range requests
high7.1Jul 24, 2026CVE-2026-73500
etcd: `tlsListener.acceptLoop` spawns unbounded handshake goroutines with no deadline
high8.7Jul 24, 2026CVE-2026-33343
etcd: Nested etcd transactions bypass RBAC authorization checks
lowNo fixMar 20, 2026CVE-2026-33413
etcd: Authorization bypasses in multiple APIs
high8.8No fixMar 20, 2026GHSA-j86v-2vjr-fg8f
Etcd Gateway TLS endpoint validation only confirms TCP reachability
mediumFeb 3, 2024GHSA-pm3m-32r3-7mfh
Etcd embed auto compaction retention negative value causing a compaction loop or a crash
lowFeb 3, 2024
