All vulnerabilities

Servers and applications

CVE-2026-33413

Authorization bypasses in multiple APIs

Severity
High 8.8
Published
20 Mar 2026
Last changed
17 Jun 2026
Added to UpHeron
1 Nov 2026
Fixed in
3.4.42, 3.5.28, 3.6.9
Exploit chance
0.3% in the next 30 daysHigher than 17% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Missing authorization (CWE-862)
Attack
Over the network · No login needed · No user action needed
Attacker can
Read some data · Change some data · Take it down
CVSS 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-q8m4-xhhv-38mg
Sources
NVD, Project advisories (GitHub)

Description

_What kind of vulnerability is it? Who is impacted?_

Multiple vulnerabilities allow unauthorized users to 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
  • 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.

_Community efforts help keep etcd secure_

From etcd-io/etcd's security advisory. Shortened; the full text is there.

Workarounds

_Is there a way for users to fix or remediate the vulnerability without upgrading?_

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
  • require strong client identity at the transport layer, such as mTLS with tightly scoped client certificate distribution
Workarounds as given by etcd-io/etcd's security advisory.

Affected software

SoftwareAffected versions
etcdServers and applications · cpe:a:etcd:etcd
  • Every version before 3.4.42
  • From 3.5.0 before 3.5.28
  • From 3.6.0 before 3.6.9
etcdServers and applications · github:etcd-io/etcd
  • Every version before 3.6.9
  • Every version before 3.5.28
  • Every version before 3.4.42

About etcd

a distributed key-value database system

From Wikidata, CC0 1.0.
GitHub stars
52,607GitHub, 15 Nov 2026
Forks
10,600GitHub, 15 Nov 2026
Latest release
v3.7.3GitHub, 15 Nov 2026
Released
22 Oct 2026GitHub
Developer
Cloud Native Computing FoundationWikidata
License
Apache Software License 2.0Wikidata
Written in
GoWikidata
First published on GitHub
6 Jul 2013GitHub

Release lines

ReleaseLatestSecurity fixes
3.73.7.3Yes
3.63.6.16Yes
3.53.5.35Until 8 Jul 2027
3.43.4.45Ended 1 Jun 2026
3.33.3.27Ended 15 Oct 2021
3.23.2.32Ended 28 Mar 2021

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-33413
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-33413
  • GitHub Advisory Database https://github.com/advisories/GHSA-q8m4-xhhv-38mg
  • github.com https://github.com/etcd-io/etcd/security/advisories/GHSA-q8m4-xhhv-38mg