Authentication bypass in go.etcd.io/etcd
Published 14 Apr 2021 · Updated 4 Feb 2026
Is your project on an affected go.etcd.io/etcd?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <0.5.0-alpha.5.0.20190108173120-83c051b701d3
- Fixed in
- 0.5.0-alpha.5.0.20190108173120-83c051b701d3
go get go.etcd.io/etcd@v0.5.0-alpha.5.0.20190108173120-83c051b701d3Details
A user can use a valid client certificate that contains a CommonName that matches a valid RBAC username to authenticate themselves as that user, despite lacking the required credentials. This may allow authentication bypass, but requires a certificate that is issued by a CA trusted by the server.
Is GO-2021-0077 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected go.etcd.io/etcd, and gives you the command that fixes it.
More advisories for go.etcd.io/etcd
- LowCVE-2026-44283etcd RBAC bypass allows unauthorized data access via PrevKv/lease attachment in nested transaction Put requests · 7 May 2026
- LowCVE-2026-33413Authorization bypasses in multiple APIs in go.etcd.io/etcd · 7 Apr 2026
- LowCVE-2026-33343Nested etcd transactions bypass RBAC authorization checks in go.etcd.io/etcd · 7 Apr 2026
- HighCVE-2026-33413etcd: Authorization bypasses in multiple APIs · 20 Mar 2026
- LowCVE-2026-33343etcd: Nested etcd transactions bypass RBAC authorization checks · 20 Mar 2026
- LowGO-2024-2527Insecure ciphers are allowed by default in go.etcd.io/etcd · 28 Jun 2024
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.