etcd - Debian Package Tracker

general

source: etcd (main)
version: 3.5.16-10
maintainer: Debian Go Packaging Team (DMD)
uploaders: Jelmer Vernooij [DMD] – Anthony Fok [DMD] – Tim Potter [DMD]
arch: all any
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 3.3.25+dfsg-6
oldstable: 3.4.23-4
stable: 3.5.16-4
testing: 3.5.16-10
unstable: 3.5.16-10
exp: 3.5.22-2

versioned links

3.3.25+dfsg-6: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.4.23-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.5.16-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.5.16-10: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.5.22-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.5.22-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

etcd-client
etcd-server
golang-etcd-server-dev

action needed

Marked for autoremoval on 12 May due to golang-google-grpc: #1132228 high

Version 3.5.16-10 of etcd is marked for autoremoval from testing on Tue 12 May 2026. It depends (transitively) on golang-google-grpc, affected by #1132228. You should try to prevent the removal by fixing these RC bugs.

Created: 2026-04-05 Last update: 2026-04-07 10:02

A new upstream version is available: 3.6.10 high

A new upstream version 3.6.10 is available, you should consider packaging it.

Created: 2025-11-27 Last update: 2026-04-07 08:00

2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:

CVE-2026-33343: 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.
CVE-2026-33413: 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.

Created: 2026-03-27 Last update: 2026-03-27 18:33

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2026-33343: 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.
CVE-2026-33413: 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.

Created: 2026-03-27 Last update: 2026-03-27 18:33

2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:

CVE-2026-33343: 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.
CVE-2026-33413: 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.

Created: 2026-03-27 Last update: 2026-03-27 18:33

6 security issues in bullseye high

There are 6 open security issues in bullseye.

2 important issues:

CVE-2026-33343: 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.
CVE-2026-33413: 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.

4 issues postponed or untriaged:

CVE-2018-1098: (needs triaging) A cross-site request forgery flaw was found in etcd 3.3.1 and earlier. An attacker can set up a website that tries to send a POST request to the etcd server and modify a key. Adding a key is done with PUT so it is theoretically safe (can't PUT from an HTML form or such) but POST allows creating in-order keys that an attacker can send.
CVE-2018-1099: (needs triaging) DNS rebinding vulnerability found in etcd 3.3.1 and earlier. An attacker can control his DNS records to direct to localhost, and trick the browser into sending requests to localhost (or any other address).
CVE-2021-28235: (needs triaging) Authentication vulnerability found in Etcd-io v.3.4.10 allows remote attackers to escalate privileges via the debug function.
CVE-2023-32082: (needs triaging) etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.26 and 3.5.9, the LeaseTimeToLive API allows access to key names (not value) associated to a lease when `Keys` parameter is true, even a user doesn't have read permission to the keys. The impact is limited to a cluster which enables auth (RBAC). Versions 3.4.26 and 3.5.9 fix this issue. There are no known workarounds.

Created: 2026-03-27 Last update: 2026-03-27 18:33

4 security issues in bookworm high

There are 4 open security issues in bookworm.

2 important issues:

CVE-2026-33343: 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.
CVE-2026-33413: 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.

2 ignored issues:

CVE-2021-28235: Authentication vulnerability found in Etcd-io v.3.4.10 allows remote attackers to escalate privileges via the debug function.
CVE-2023-32082: etcd is a distributed key-value store for the data of a distributed system. Prior to versions 3.4.26 and 3.5.9, the LeaseTimeToLive API allows access to key names (not value) associated to a lease when `Keys` parameter is true, even a user doesn't have read permission to the keys. The impact is limited to a cluster which enables auth (RBAC). Versions 3.4.26 and 3.5.9 fix this issue. There are no known workarounds.

Created: 2023-06-10 Last update: 2026-03-27 18:33

lintian reports 7 warnings normal

Lintian reports 7 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2025-10-12 Last update: 2026-01-03 04:00

debian/patches: 16 patches to forward upstream low

Among the 23 debian patches available in version 3.5.16-10 of the package, we noticed the following issues:

16 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-02-09 12:19

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.2).

Created: 2025-12-23 Last update: 2026-03-31 15:01

news

[rss feed]

[2026-02-11] etcd 3.5.16-10 MIGRATED to testing (Debian testing watch)
[2026-02-08] Accepted etcd 3.5.16-10 (source) into unstable (Reinhard Tartler)
[2026-01-06] etcd 3.5.16-9 MIGRATED to testing (Debian testing watch)
[2026-01-02] Accepted etcd 3.5.16-9 (source) into unstable (Daniel Swarbrick)
[2025-10-17] etcd 3.5.16-8 MIGRATED to testing (Debian testing watch)
[2025-10-12] Accepted etcd 3.5.16-8 (source) into unstable (Reinhard Tartler)
[2025-08-22] etcd 3.5.16-7 MIGRATED to testing (Debian testing watch)
[2025-08-18] Accepted etcd 3.5.16-7 (source) into unstable (Reinhard Tartler)
[2025-08-17] Accepted etcd 3.5.16-6 (source) into unstable (Reinhard Tartler)
[2025-08-17] Accepted etcd 3.5.16-5 (source) into unstable (Reinhard Tartler)
[2025-08-17] Accepted etcd 3.5.22-2 (source) into experimental (Reinhard Tartler)
[2025-08-15] Accepted etcd 3.5.22-1 (source) into experimental (Reinhard Tartler)
[2025-03-09] etcd 3.5.16-4 MIGRATED to testing (Debian testing watch)
[2025-03-04] Accepted etcd 3.5.16-4 (source) into unstable (Guillem Jover)
[2024-11-06] etcd 3.5.16-3 MIGRATED to testing (Debian testing watch)
[2024-11-01] Accepted etcd 3.5.16-3 (source) into unstable (Reinhard Tartler)
[2024-10-31] Accepted etcd 3.5.16-2 (source) into unstable (Reinhard Tartler)
[2024-10-21] Accepted etcd 3.5.16-1 (source) into experimental (Reinhard Tartler)
[2024-08-15] etcd 3.5.15-7 MIGRATED to testing (Debian testing watch)
[2024-08-09] Accepted etcd 3.5.15-7 (source) into unstable (Reinhard Tartler)
[2024-08-07] etcd 3.5.15-6 MIGRATED to testing (Debian testing watch)
[2024-08-03] Accepted etcd 3.5.15-6 (source) into unstable (Reinhard Tartler)
[2024-08-03] Accepted etcd 3.5.15-5 (source) into unstable (Mathias Gibbens)
[2024-08-01] Accepted etcd 3.5.15-4 (source) into unstable (Shengjing Zhu)
[2024-07-30] Accepted etcd 3.5.15-3 (source) into unstable (Mathias Gibbens)
[2024-07-29] Accepted etcd 3.5.15-2 (source) into unstable (Mathias Gibbens)
[2024-07-28] Accepted etcd 3.5.15-1 (source) into unstable (Reinhard Tartler)
[2024-06-29] Accepted etcd 3.4.30-3 (source) into experimental (Reinhard Tartler)
[2024-06-09] Accepted etcd 3.4.30-2 (source) into experimental (Reinhard Tartler)
[2024-03-15] etcd 3.4.30-1 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 5
RC: 0
I&N: 2
M&W: 3
F&P: 0
patch: 0

links

homepage
lintian (0, 7)
buildd: logs, exp, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.5.16-10
10 bugs