Echoのプロキシに接続が残り続ける脆弱性、DoSのおそれ
Summary
Echoのプロキシ機能で、WebSocketクライアントが切断された後もハンドラーや接続が解放されず残ることがあり、繰り返されるとサービス妨害(DoS)につながるおそれがあります。影響を受けるのはv4.15.0からv4.16.0、およびv5.0.0からv5.4.0です。修正版はv4.16.1とv5.4.1で、アップグレードで対応できます。
AI summary
Written by an external AI model and may contain mistakes. Check the original description and references below before acting on it.
Echoのプロキシ機能で、WebSocketクライアントが切断された後もハンドラーや接続が解放されず残ることがあり、繰り返されるとサービス妨害(DoS)につながるおそれがあります。影響を受けるのはv4.15.0からv4.16.0、およびv5.0.0からv5.4.0です。修正版はv4.16.1とv5.4.1で、アップグレードで対応できます。
Affected packages
| Ecosystem | Package | Affected | Fixed |
|---|---|---|---|
| labstack | echo | — | — |
| go | github.com/labstack/echo/v4 |
≥ 4.15.0, < 4.16.1 |
4.16.1 |
| go | github.com/labstack/echo/v5 |
≥ 5.0.0, < 5.4.1 |
5.4.1 |
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-118262 golang-github-labstack-echo
Original description The description as published by the source.
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.
Workarounds
Disable WebSocket proxy routes un…
Source: CVE.org (CVE Program・cvelistV5) NVD GitHub Advisory