Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73500

Vulnerability in go.etcd.io/etcd/v3 (CVE-2026-73500)

Summary

Vulnerability in go.etcd.io/etcd/v3 (CVE-2026-73500). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.5.33 or later.

Original description

The description as published by the source.

In go.etcd.io/etcd/client/pkg/v3 before 3.5.33, 3.6.14, and 3.7.1, TLS handshakes on listeners created by NewTLSListener do not enforce a handshake deadline. An unauthenticated network attacker who connects to an etcd TLS listener without sending a ClientHello causes a goroutine and a tracking map entry to block indefinitely. Opening many such connections exhausts memory, leading to a denial of service.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

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-73500 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.33 or later.
If unsure, ask your IT team or search "go.etcd.io/etcd/v3 CVE-2026-73500" on the vendor's site.

CVE-2026-73500 (go.etcd.io/etcd/v3) — CWE-770
Patched: 3.5.33 — apply immediately
Workaround: then restrict network access.
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.

❓ What is the problem

A vulnerability (CWE-770) exists in go.etcd.io/etcd/v3.

📍 Affected scope

Check the vendor advisory for the affected versions of go.etcd.io/etcd/v3.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.5.33.

🛡️ Workaround

Workaround: then restrict network access.

🔍 Detection

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    then restrict network access.

    パッチが適用されるまでの応急処置として、then restrict network access. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade go.etcd.io/etcd/v3 to 3.5.33

    ステージング環境で 3.5.33 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go go.etcd.io/etcd/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.5.33"}]}]
Bitnami etcd
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.5.33"},{"introduced":"3.6.0"},{"fixed":"3.6.14"},{"introduced":"3.7.0"},{"fixed":"3.7.1"}]}]
Go go.etcd.io/etcd/client/pkg/v3
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"3.5.33"},{"introduced":"3.6.0"},{"fixed":"3.6.14"},{"introduced":"3.7.0-alpha.0"},{"fixed":"3.7.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details