How severe is GHSA-6vch-q96h-7gc3?

No CVSS score has been assigned to GHSA-6vch-q96h-7gc3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6vch-q96h-7gc3?

GHSA-6vch-q96h-7gc3 affects the following packages: go.etcd.io/etcd/v3 (Go), go.etcd.io/etcd/v3 (Go), go.etcd.io/etcd/v3 (Go). Ecosystems affected: Go.

How do I fix GHSA-6vch-q96h-7gc3?

Update go.etcd.io/etcd/v3 to 3.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6vch-q96h-7gc3 is resolved across your whole dependency graph.

How do I detect GHSA-6vch-q96h-7gc3 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.etcd.io/etcd/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6vch-q96h-7gc3 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-6vch-q96h-7gc3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6vch-q96h-7gc3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6vch-q96h-7gc3?

GHSA-6vch-q96h-7gc3 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 51th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6vch-q96h-7gc3?

GHSA-6vch-q96h-7gc3 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6vch-q96h-7gc3 published, and has it been updated?

GHSA-6vch-q96h-7gc3 was published on July 24, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-6vch-q96h-7gc3 — v3

Fix: etcd-io/etcd#22130

GHSA-6vch-q96h-7gc3 is a CWE-770 vulnerability in go.etcd.io/etcd/v3. A fix is available for go.etcd.io/etcd/v3 — see the affected versions and patch details below.

etcd: `tlsListener.acceptLoop` spawns unbounded handshake goroutines with no deadline

Also known asBIT-etcd-2026-73500CVE-2026-73500GO-2026-6107

Published

Jul 24, 2026

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6vch-q96h-7gc3.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🐹go.etcd.io/etcd/v3🐹go.etcd.io/etcd/v3🐹go.etcd.io/etcd/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

What kind of vulnerability is it? Who is impacted?

A network attacker who can reach an etcd TLS listener can open many TCP connections and never send a ClientHello. Each connection spawns a goroutine in the etcd server process that blocks indefinitely inside tls.Conn.Handshake(), and each is tracked in the pending map. Unbounded goroutine and map growth exhausts memory in the etcd process, causing loss of availability for the etcd cluster (and, when etcd backs Kubernetes, the control plane).

Patches

Has the problem been patched? What versions should users upgrade to?

This vulnerability is patched in the following versions:

etcd 3.7.1
etcd 3.6.14
etcd 3.5.33

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

If upgrading is not immediately possible, then restrict network access. Limit which hosts can reach etcd's client (gRPC) port via firewall rules or network policy, reducing who can attempt exploitation.

Reporter

VMware By Broadcom

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`go.etcd.io/etcd/v3`	≥ 3.7.0-alpha.0&&< 3.7.1	3.7.1`go get go.etcd.io/etcd/v3@v3.7.1`
🐹Go	`go.etcd.io/etcd/v3`	≥ 3.6.0&&< 3.6.14	3.6.14`go get go.etcd.io/etcd/v3@v3.6.14`
🐹Go	`go.etcd.io/etcd/v3`	all versions	3.5.33`go get go.etcd.io/etcd/v3@v3.5.33`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.etcd.io/etcd/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update go.etcd.io/etcd/v3 to 3.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6vch-q96h-7gc3 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This is an Important denial of service flaw in etcd, a critical component for distributed systems and Kubernetes control planes. A remote attacker can exhaust etcd memory by initiating numerous incomplete TLS handshakes, leading to a loss of availability for affected clusters.

Workaround published by Red Hat

Restrict network access to the etcd TLS listener to only trusted clients and networks. Configure firewall rules to limit inbound connections to the etcd client port (default 2379) and peer port (default 2380) to authorized hosts. This reduces the attack surface by preventing untrusted network attackers from reaching the vulnerable service.

Source: Red Hat security advisory for GHSA-6vch-q96h-7gc3 (CC BY 4.0)

Product	Fixed in	Advisory
Multicluster Global Hub 1.4.9	`multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1788375682`	RHSA-2026:67516
Multicluster Global Hub 1.5.8	`multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1789515639`	RHSA-2026:71597
Red Hat Hardened Images	`etcd-main-3.7.1-0.1.hum1`	RHSA-2026:44868
Red Hat Trusted Artifact Signer 1.3	`rhtas/createtree-rhel9:1789645873`	RHSA-2026:70826
Red Hat Trusted Artifact Signer 1.3	`rhtas/updatetree-rhel9:1789645873`	RHSA-2026:70828
Red Hat Trusted Artifact Signer 1.3	`rhtas/certificate-transparency-rhel9:1789655058`	RHSA-2026:70829

Frequently Asked Questions

### Impact _What kind of vulnerability is it? Who is impacted?_ A network attacker who can reach an etcd TLS listener can open many TCP connections and never send a ClientHello. Each connection spawns a goroutine in the etcd server process that blocks indefinitely inside tls.Conn.Handshake(), and each is tracked in the pending map. Unbounded goroutine and map growth exhausts memory in the etcd process, causing loss of availability for the etcd cluster (and, when etcd backs Kubernetes, the control plane). ### Patches _Has the problem been patched? What versions should users upgrade to?_ This

O3 Security · Impact-Aware SCA

Is GHSA-6vch-q96h-7gc3 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works