CVE-2026-33413: etcd: Authorization bypasses in multiple APIs
Impact What kind of vulnerability is it? Who is impacted? Multiple vulnerabilities allow unauthorized users to bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients.
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?_
Multiple vulnerabilities allow unauthorized users to bypass authentication or authorization checks and call certain etcd functions in clusters that expose the gRPC API to untrusted or partially trusted clients.
In unpatched etcd clusters with etcd auth enabled, unauthorized users are able to:
- call MemberList and learn cluster topology, including member IDs and advertised endpoints
- call Alarm, which can be abused for operational disruption or denial of service
- use Lease APIs, interfering with TTL-based keys and lease ownership
- trigger compaction, permanently removing historical revisions and disrupting watch, audit, and recovery workflows
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?_
These vulnerabilities are 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
_Community efforts help keep etcd secure_
The etcd community thanks Isaac David, bugbunny.ai, Asim Viladi Oglu Manizada, Alex Schapiro & Ahmed Allam from Strix security, Luke Francis, and @OLU-DEVX for reporting these vulnerabilities.
Dependency Between Reported Issues
These issues all originate from the same underlying flaw in the gRPC API layer.
They affect the same API surface and share a common root cause. In practice, the fix is implemented as a single, unified change at the API layer, which resolves all issues together.
Given this, we believe these issues are best treated as a single vulnerability and should be assigned a single CVE.
Credited to manizada.
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-44283
etcd RBAC bypass allows unauthorized data access via PrevKv/lease attachment in nested transaction Put requests
lowMay 7, 2026CVE-2026-33343
etcd: Nested etcd transactions bypass RBAC authorization checks
lowNo 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
