CVE-2026-33343: vulnerability in etcd-io etcd
etcd: Nested etcd transactions bypass RBAC authorization checks
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
3Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 0epss 0.2%
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, 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. 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 require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N
Affected products
etcd-io · etcdRelated CVEs — etcd-io etcd
In the same product, most dangerous first.
CVE-2020-15136MEDIUMImproper authentication in etcdEPSS 1.7%CVE-2020-15115MEDIUMNo minimum password length in etcdEPSS 1.3%CVE-2020-15112MEDIUMImproper Input Validation in etcdEPSS 1.3%CVE-2020-15106MEDIUMImproper Input Validation in etcdEPSS 1.3%CVE-2020-15114HIGHDenial of Service in etcdEPSS 1.1%CVE-2023-32082LOWetcd key name can be accessed via LeaseTimeToLive APIEPSS 0.7%