Authorization Flaw in go.etcd.io/etcd/v3 (CVE-2026-44283)
Summary
Vulnerability in go.etcd.io/etcd/v3 (CVE-2026-44283). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.5.30 or later.
Original description
The description as published by the source.
etcd is a distributed key-value store for the data of a distributed system. Prior to 3.4.44, 3.5.30, and 3.6.11, a vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user without sufficient read or lease-related permissions may be able to access unauthorized data or attach leases by invoking transaction operations with these features enabled. This vulnerability is fixed in 3.4.44, 3.5.30, and 3.6.11.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44283 has been found in go.etcd.io/etcd/v3.
Risk of unauthorized operations or information disclosure.
What to do: upgrade go.etcd.io/etcd/v3 to 3.5.30 or later.
If unsure, ask your IT team or search "go.etcd.io/etcd/v3 CVE-2026-44283" on the vendor's site.
CVE-2026-44283 (go.etcd.io/etcd/v3) — CWE-863
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.5.30 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Incorrect authorization (CWE-863) exists in go.etcd.io/etcd/v3.
Check the vendor advisory for the affected versions of go.etcd.io/etcd/v3.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.5.30.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'go.etcd.io/etcd/v3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'go.etcd.io/etcd/v3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
go.etcd.io/etcd/v3を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade go.etcd.io/etcd/v3 to 3.5.30ステージング環境で 3.5.30 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-44283 etcd Fixed in: 3.6.11-r1
- Debian DEBIAN-CVE-2026-44283 etcd
- Ubuntu UBUNTU-CVE-2026-44283 etcd
References
- advisory github.com
- package github.com
- web nvd.nist.gov
- web github.com