Is go.etcd.io/etcd/v3 3.2 vulnerable?
Go · 33 releases from 3.2.0 to 3.2.32 · latest go.etcd.io/etcd/v3 is 3.7.3 · checked 18 Nov 2026
Yes: 15 known advisories
Yes. go.etcd.io/etcd/v3 3.2.32, the last 3.2 release, is affected by 15 known security advisories (4 high, 2 medium, 9 low), including CVE-2026-73500, CVE-2026-73499, CVE-2026-33413. 1 more affects earlier 3.2.x releases. At least one has no fixed release yet.
Is your project on an affected go.etcd.io/etcd/v3?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting go.etcd.io/etcd/v3 3.2.32
etcd: `tlsListener.acceptLoop` spawns unbounded handshake goroutines with no deadline
- Affected
- >=3.7.0-alpha.0 <3.7.1 · >=3.6.0 <3.6.14 · <3.5.33
- Fixed in
- 3.5.33, 3.6.14, 3.7.1
etcd: Watch API authorization bypass via open-ended range requests
- Affected
- >=3.7.0-alpha.0 <3.7.1 · >=3.6.0 <3.6.14 · <3.5.33
- Fixed in
- 3.5.33, 3.6.14, 3.7.1
Authorization bypasses in multiple APIs in go.etcd.io/etcd
- Affected
- <3.4.42 · >=3.5.0-alpha.0 <3.5.28 · >=3.6.0-alpha.0 <3.6.9
- Fixed in
- 3.4.42, 3.5.28, 3.6.9
Nested etcd transactions bypass RBAC authorization checks in go.etcd.io/etcd
- Affected
- <3.4.42 · >=3.5.0-alpha.0 <3.5.28 · >=3.6.0-alpha.0 <3.6.9
- Fixed in
- 3.4.42, 3.5.28, 3.6.9
etcd: Authorization bypasses in multiple APIs
- Affected
- >=3.6.0-alpha.0 <3.6.9 · >=3.5.0-alpha.0 <3.5.28 · <3.4.42
- Fixed in
- 3.4.42, 3.5.28, 3.6.9
etcd: Nested etcd transactions bypass RBAC authorization checks
- Affected
- >=3.6.0-alpha.0 <3.6.9 · >=3.5.0-alpha.0 <3.5.28 · <3.4.42
- Fixed in
- 3.4.42, 3.5.28, 3.6.9
Etcd Gateway TLS endpoint validation only confirms TCP reachability in go.etcd.io/etcd
- Affected
- All versions
- Fixed in
- No fix released
Etcd embed auto compaction retention negative value causing a compaction loop or a crash in go.etcd.io/etcd
- Affected
- All versions
- Fixed in
- No fix released
Etcd auth Inaccurate logging of authentication attempts for users with CN-based auth only in go.etcd.io/etcd
- Affected
- All versions
- Fixed in
- No fix released
Etcd auth Inaccurate logging of authentication attempts for users with CN-based auth only
- Affected
- >=3.4.0-rc.0 <3.4.10 · <3.3.23
- Fixed in
- 3.3.23, 3.4.10
Etcd embed auto compaction retention negative value causing a compaction loop or a crash
- Affected
- >=3.4.0-rc.0 <3.4.10 · <3.3.23
- Fixed in
- 3.3.23, 3.4.10
Etcd Gateway TLS endpoint validation only confirms TCP reachability
- Affected
- >=3.4.0-rc.0 <3.4.10 · <3.3.23
- Fixed in
- 3.3.23, 3.4.10
etcd vulnerable to TOCTOU of gateway endpoint authentication
- Affected
- >=3.4.0 <3.4.10 · <3.3.23
- Fixed in
- 3.3.23, 3.4.10
etcd's WAL `ReadAll` method vulnerable to an entry with large index causing panic
- Affected
- <3.3.23 · >=3.4.0 <3.4.10
- Fixed in
- 3.3.23, 3.4.10
etcd Cross-site Request Forgery (CSRF)
- Affected
- <3.4.0
- Fixed in
- 3.4.0
Fixed within 3.2.x, affecting earlier releases
go.etcd.io/etcd Authentication Bypass
- Affected
- >=3.2.0 <3.2.26 · >=3.3.0 <3.3.11
- Fixed in
- 3.2.26, 3.3.11
Every go.etcd.io/etcd/v3 3.2.x release
Affected: 3.2.0 to 3.2.32. Latest go.etcd.io/etcd/v3: 3.7.3.
| Version | Known advisories |
|---|---|
| go.etcd.io/etcd/v3 3.2.32 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.31 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.30 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.29 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.28 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.27 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.26 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.25 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.24 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.23 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.22 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.21 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.20 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.19 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.18 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.17 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.16 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.15 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.14 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.13 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.12 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.11 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.10 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.9 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.8 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.7 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.6 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.5 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.4 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.3 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.2 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.1 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
| go.etcd.io/etcd/v3 3.2.0 | CVE-2026-73500, CVE-2026-73499, CVE-2026-33413, CVE-2026-33343, CVE-2026-33413, CVE-2026-33343, GO-2024-2528, GO-2024-2529, GO-2024-2530, GHSA-vjg6-93fv-qv64, GHSA-pm3m-32r3-7mfh, GHSA-j86v-2vjr-fg8f, GHSA-h8g9-6gvh-5mrc, CVE-2020-15106, CVE-2018-16886, CVE-2018-1098 |
Which of your client projects are still on go.etcd.io/etcd/v3 3.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact go.etcd.io/etcd/v3 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other go.etcd.io/etcd/v3 versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.