NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2026-33343: etcd: Nested etcd transactions bypass RBAC authorization checks

lowGHSA-rfx7-8w68-q57q

Impact What kind of vulnerability is it? Who is impacted? An authenticated user with RBAC restricted permissions on key ranges can use nested transactions to bypass all key-level authorization. This allows any authenticated user with direct access to etcd to effectively ignore all key range restrictions, accessing the entire etcd data store.

Published Mar 20, 2026 · Updated Mar 27, 2026

Affected packages

go.etcd.io/etcd/v3

Ecosystem
Go
Affected
>= 3.6.0-alpha.0, <= 3.6.8
Fixed in
3.6.9
Check
go list -m go.etcd.io/etcd/v3

go.etcd.io/etcd/v3

Ecosystem
Go
Affected
>= 3.5.0-alpha.0, <= 3.5.27
Fixed in
3.5.28
Check
go list -m go.etcd.io/etcd/v3

go.etcd.io/etcd/v3

Ecosystem
Go
Affected
<= 3.4.41
Fixed in
3.4.42
Check
go list -m go.etcd.io/etcd/v3

go.etcd.io/etcd

Ecosystem
Go
Affected
<= 3.3.27
Fixed in
No patched version yet
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?_

An authenticated user with RBAC restricted permissions on key ranges can use nested transactions to bypass all key-level authorization. This allows any authenticated user with direct access to etcd to effectively ignore all key range restrictions, accessing the entire etcd data store.

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.9
  • etcd 3.5.28
  • etcd 3.4.42

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

_Our community helps keep etcd secure_

SIG-Etcd thanks community members Luke Francis and Battulga Byambaa for reporting this vulnerability.

Credited to burg0w.

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 entries