CVE-2026-118262

Echo: WebSocket proxy can retain connections and handlers after client disconnect

Published Oct 28, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
Description
Echo is a Go web framework. From 4.15.0 until 4.16.1 and 5.4.1, Echo's Proxy middleware can retain a handler, copy goroutines, and network connections after a WebSocket client disconnects when the upstream keeps its connection open. The raw proxy waits for both copy directions without reliably closing the peer connection when one direction ends, including when a rejected upgrade response uses HTTP keep-alive. Repeated connections can accumulate resources and cause denial of service, depending on proxy-route accessibility, upstream behavior, and connection deadlines. This issue is fixed in 4.16.1 and 5.4.1.

Analysis

AI-generated

Technical impact

Echo’s Proxy middleware can retain goroutine handlers, network connections, and copies of data after a WebSocket client disconnects if the upstream keeps the connection open. The proxy waits for both copy directions without reliably closing the peer connection once one side ends, including cases where a rejected upgrade response uses HTTP keep‑alive. This behavior can cause repeated connections to accumulate resources, leading to a denial of service depending on the proxy‑route accessibility, upstream behavior, and connection deadlines. The weakness is a retained resource mechanism, classified as CWE‑772.

Affected Systems

Versions of the Echo Go framework from 4.15.0 through 4.16.1 and 5.4.1 are affected. All deployments using Echo’s Proxy middleware within these ranges are potentially vulnerable.

Risk and Exploitability

The CVSS score is 8.2, indicating a high severity. The EPSS score is not available, so the current likelihood of exploitation is unknown. Echo is not listed in the CISA KEV catalog. The likely attack vector is an attacker opening multiple WebSocket connections to a proxy‑enabled route and causing the upstream to maintain open connections, which can lead to resource exhaustion. Without a patch, repeated connections can accumulate until the target application experiences a denial of service.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Echo to version 4.16.1 or later, or 5.4.1 or later, to apply the fixed proxy logic.
  • If upgrading immediately is not possible, restrict or disable the Echo Proxy middleware on critical routes to prevent unintended resource retention.
  • Configure upstream services and Echo to enforce timeouts and connection limits to reduce the impact of retained connections.

Generated by OpenCVE AI on October 28, 2026 at 21:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-9969-6676-49h5 Echo: WebSocket proxy can retain connections and handlers after client disconnect
History
Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Important

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Labstack
Labstack echo
Vendors & Products Labstack
Labstack echo
Type Values Removed Values Added
Description Echo is a Go web framework. From 4.15.0 until 4.16.1 and 5.4.1, Echo's Proxy middleware can retain a handler, copy goroutines, and network connections after a WebSocket client disconnects when the upstream keeps its connection open. The raw proxy waits for both copy directions without reliably closing the peer connection when one direction ends, including when a rejected upgrade response uses HTTP keep-alive. Repeated connections can accumulate resources and cause denial of service, depending on proxy-route accessibility, upstream behavior, and connection deadlines. This issue is fixed in 4.16.1 and 5.4.1.
Title Echo: WebSocket proxy can retain connections and handlers after client disconnect
Weaknesses CWE-772
References
Metrics cvssV4_0

{'score': 8.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-772

    Missing Release of Resource after Effective Lifetime

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 3, 2026, 1:24 PM
Reserved
Oct 27, 2026, 8:13 PM
Status
Undergoing Analysis
Published
Oct 28, 2026, 7:17 PM
Modified
Nov 4, 2026, 11:10 PM
Severity
Important
Public date
Oct 28, 2026, 7:00 PM