Live › vulnerability › GHSA-9969-6676-49h5
Go to dashboardEcho's Proxy middleware did not reliably release handlers, goroutines and network connections after a WebSocket client disconnected while the upstream kept its connection open. An attacker who repeatedly opens such connections can accumulate server resources and cause a denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 20:59 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/labstack/echo/v4 | go | >= 4.15.0, < 4.16.1 | 4.16.1 |
| github.com/labstack/echo/v5 | go | >= 5.0.0, < 5.4.1 | 5.4.1 |
4.16.1 or github.com/labstack/echo/v5 below 5.4.1v4.16.1 or github.com/labstack/echo/v5 v5.4.1Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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 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.
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.
Reported by @irisitymichaelgrundberg.
This page as .md · .json · in your agent: get_signal("GHSA-9969-6676-49h5")
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.