8.8

CVE-2026-33413: etcd-io etcd Missing Authorization

CVSS: 8.8v4.0HighAnalyzed
AliasesUBUNTU-CVE-2026-33413DEBIAN-CVE-2026-33413CGA-22hq-3ch7-82vx
Published 26-03-2026Last modified 26-03-2026

Vulnerability summary

CVE-2026-33413 is a high (CVSS 8.8) Missing Authorization vulnerability in etcd-io etcd. EPSS estimates a 0.34% chance of exploitation in the next 30 days, higher than 25.4% of scored vulnerabilities.

Overall risk
35/100
0100
Medium · default modelHow is this calculated?
CVSS score
8.8/10
010
High · v4.0 (CVE.org)
EPSS score
0.34%
0%100%
Low · +0.09 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 3 · Related 2

Timeline

  1. 26-03-2026
    PublishedVulnerability first disclosed.
  2. 26-03-2026
    Last modifiedVulnerability information updated.

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.

CVSS metrics

9 scores · 7 sources · 2 versions

EPSS trend

Probability

0.34%

Chance of exploitation in the next 30 days

Percentile

25%

Versus all other CVEs

30-day change

+0.09 pp

From 0.25% on 19-09-2026

19-09-202619-10-2026
EPSS score
0.34%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Chainguard8 products
  • etcd-3.4< 3.4.45-r0
  • juicefs-1.2All versions (No fix recorded)
  • juicefs-1.3< 1.3.1-r22
  • py3-etcdAll versions (No fix recorded)
  • py3.10-etcdAll versions (No fix recorded)
Wolfi6 products
  • juicefs-1.3< 1.3.1-r22
  • py3-etcdAll versions (No fix recorded)
  • py3.10-etcdAll versions (No fix recorded)
  • py3.11-etcdAll versions (No fix recorded)
  • py3.12-etcdAll versions (No fix recorded)
Debian1 product
  • etcdAll versions (No fix recorded) | < 3.5.16-11
Etcd1 product
  • etcd< 3.4.42 | ≥ 3.5.0, < 3.5.28 | ≥ 3.6.0, < 3.6.9
Etcd-io1 product
  • etcd≥ 3.6.0-alpha.0, < 3.6.9 | ≥ 3.5.0-alpha.0, < 3.5.28 | < 3.4.42
Go.etcd.io1 product
  • etcd≤ 3.3.27 | All versions (No fix recorded)
Go.etcd.io/etcd1 product
  • v3≥ 3.5.0-alpha.0, < 3.5.28 | < 3.4.42 | ≥ 3.6.0-alpha.0, < 3.6.9
Opensuse1 product
  • flannel&distro=openSUSE Tumbleweed< 0.28.4-1.1
Ubuntu1 product
  • etcdAll versions (No fix recorded)

9 vendors · 21 products

References

8 links