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.
Github GHSA