Authorization Bypass Through User-Controlled Key Affecting etcd package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.21% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-ETCD-15808246
  • published29 Mar 2026
  • disclosed26 Mar 2026

Introduced: 26 Mar 2026

CVE-2026-33343  (opens in a new tab)
CWE-639  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 etcd.

NVD Description

Note: Versions mentioned in the description apply only to the upstream etcd package and not the etcd package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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 Base Scores

version 3.1