GHSA-9969-6676-49h5: Echo: WebSocket proxy can retain connections and handlers after client disconnect
(updated )
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.
References
- github.com/advisories/GHSA-9969-6676-49h5
- github.com/labstack/echo/commit/1855061e572ae9dab727c811d8382f266bfbaaec
- github.com/labstack/echo/commit/3fb0ba7e17645bb65611e2a08875d0a2f65c421f
- github.com/labstack/echo/releases/tag/v4.16.1
- github.com/labstack/echo/releases/tag/v5.4.1
- github.com/labstack/echo/security/advisories/GHSA-9969-6676-49h5
- nvd.nist.gov/vuln/detail/CVE-2026-118262
Code Behaviors & Features
Detect and mitigate GHSA-9969-6676-49h5 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →