CVE-2026-118262: Echo: WebSocket proxy can retain connections and handlers after client disconnect
Impact
Echo's Proxy middleware could retain a handler, copy goroutines and network connections after a WebSocket client disconnected if the upstream kept its connection open. The raw proxy waited for both copy directions to finish without reliably closing the other connection when one direction ended. Rejected upgrade responses with HTTP keep-alive were one way to trigger this behavior.
Repeated connections can accumulate resources and cause denial of service. The impact depends on the proxy route's accessibility, upstream behavior and configured connection deadlines. This is a medium-severity resource-retention issue; no confidentiality or integrity impact is claimed.
Affected versions and patch
Affected versions are v4.15.0 through v4.16.0 and v5.0.0 through v5.4.0. The regression was introduced by commit e2133320c7, merged in #2852.
Upgrade to v4.16.1 or v5.4.1. The patch uses Go's HTTP reverse proxy, preserves ordinary HTTP handling for rejected upgrades, and closes both sides of a WebSocket tunnel when either direction ends. It also covers an upstream that receives client EOF but deliberately keeps its side open.
Fix commits: v4, v5.
Workarounds
Disable WebSocket proxy routes until upgrading, or apply bounded connection lifetimes and resource limits at the frontend and upstream. Server idle timeouts alone may not cover hijacked WebSocket connections.
Credits
Reported by @irisitymichaelgrundberg.
Other sources
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.
— Debian
Echo: WebSocket proxy can retain connections and handlers after client disconnect in github.com/labstack/echo
— OSV
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/labstack/echo/v4to a version that resolves this vulnerability.Fixed in 4.16.1 - Upgrade
Upgrade
go/github.com/labstack/echo/v5to a version that resolves this vulnerability.Fixed in 5.4.1 - Upgrade
Upgrade
github.com/labstack/echoto a version that resolves this vulnerability.Fixed in v4.16.1 - Upgrade
Upgrade
github.com/labstack/echoto a version that resolves this vulnerability.Fixed in v5.4.1 - Configuration
Disable WebSocket proxy routes until upgrading.
Echo Proxy middleware WebSocket proxy routes = disabled - Compensating control
Apply bounded connection lifetimes and resource limits at the frontend and upstream until upgrading.
Event History
Frequently Asked Questions
Which deployments are most exposed to resource exhaustion?
Deployments with accessible Proxy middleware routes that proxy WebSocket traffic are exposed when their upstream can keep connections open after a client disconnects. Repeated connections can accumulate retained handlers, copy goroutines, and network connections, with the impact also depending on configured connection deadlines.
What conditions are needed to trigger the retention?
A WebSocket client must disconnect while the upstream connection remains open. The issue can also occur when an upgrade is rejected and the response uses HTTP keep-alive, because the raw proxy may wait for both copy directions without reliably closing the peer connection.
Are supported fixed releases available?
Yes. The issue is fixed in Echo 4.16.1 and 5.4.1. Affected versions begin at 4.15.0 and continue until those fixed releases.