CVE-2026-33413 | etcd-io etcd up to 3.4.41/3.5.27/3.6.8 gRPC API authorization
VulDBArchived Mar 26, 2026✓ Full text saved
A vulnerability, which was classified as critical , has been found in etcd-io etcd up to 3.4.41/3.5.27/3.6.8 . The impacted element is an unknown function of the component gRPC API . Performing a manipulation results in missing authorization. This vulnerability was named CVE-2026-33413 . The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-353614 · CVE-2026-33413 · GCVE-0-2026-33413
ETCD-IO ETCD UP TO 3.4.41/3.5.27/3.6.8 GRPC API AUTHORIZATION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.0 $0-$5k 1.76+
Summaryinfo
A vulnerability, which was classified as critical, was found in etcd-io etcd up to 3.4.41/3.5.27/3.6.8. This affects an unknown function of the component gRPC API. Executing a manipulation can lead to authorization. The identification of this vulnerability is CVE-2026-33413. The attack may be launched remotely. There is no exploit available. You should upgrade the affected component.
Detailsinfo
A vulnerability has been found in etcd-io etcd up to 3.4.41/3.5.27/3.6.8 and classified as critical. This vulnerability affects some unknown functionality of the component gRPC API. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability was named CVE-2026-33413 since 03/19/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available.
Upgrading to version 3.4.42, 3.5.28 or 3.6.9 eliminates this vulnerability.
Productinfo
Vendor
etcd-io
Name
etcd
Version
3.4.0
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
3.4.7
3.4.8
3.4.9
3.4.10
3.4.11
3.4.12
3.4.13
3.4.14
3.4.15
3.4.16
3.4.17
3.4.18
3.4.19
3.4.20
3.4.21
3.4.22
3.4.23
3.4.24
3.4.25
3.4.26
3.4.27
3.4.28
3.4.29
3.4.30
3.4.31
3.4.32
3.4.33
3.4.34
3.4.35
3.4.36
3.4.37
3.4.38
3.4.39
3.4.40
3.4.41
3.5.0
3.5.1
3.5.2
3.5.3
3.5.4
3.5.5
3.5.6
3.5.7
3.5.8
3.5.9
3.5.10
3.5.11
3.5.12
3.5.13
3.5.14
3.5.15
3.5.16
3.5.17
3.5.18
3.5.19
3.5.20
3.5.21
3.5.22
3.5.23
3.5.24
3.5.25
3.5.26
3.5.27
3.6.0
3.6.1
3.6.2
3.6.3
3.6.4
3.6.5
3.6.6
3.6.7
3.6.8
Website
Product: https://github.com/etcd-io/etcd/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Authorization
CWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: etcd 3.4.42/3.5.28/3.6.9
Timelineinfo
03/19/2026 CVE reserved
03/26/2026 +7 days Advisory disclosed
03/26/2026 +0 days VulDB entry created
03/26/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-33413 (🔒)
GCVE (CVE): GCVE-0-2026-33413
GCVE (VulDB): GCVE-100-353614
Entryinfo
Created: 03/26/2026 14:59
Changes: 03/26/2026 14:59 (66)
Complete: 🔍
Cache ID: 99:F0C:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸