CVE-2026-33413 — etcd: Authorization bypasses in multiple APIs

Affected: etcd-io etcd

etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.42, 3.5.28, and 3.6.9, unauthorized users may 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; and/or 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. Versions 3.4.42, 3.5.28, and 3.6.9 contain a patch. 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 and/or require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.

GHSA-q8m4-xhhv-38mg — etcd: Authorization bypasses in multiple APIs

Affected: Go: go.etcd.io/etcd/v3, Go: go.etcd.io/etcd

### 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 mTL…

Most recent entries from all

CVE-2026-33413 — etcd: Authorization bypasses in multiple APIs

GHSA-q8m4-xhhv-38mg — etcd: Authorization bypasses in multiple APIs