GitHub Advisory Database15 days ago
Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls
Impact Echo's Proxy middleware selected a raw tunnel when the client requested a WebSocket upgrade, before validating whether the configured upstream accepted it. If the upstream returned an ordinary HTTP response and kept the connection alive, subsequent HTTP requests on that co
Published October 23, 2026 · 8:49 PM
Impact Echo's Proxy middleware selected a raw tunnel when the client requested a WebSocket upgrade, before validating whether the configured upstream accepted it. If the upstream returned an ordinary HTTP response and kept the connection alive, subsequent HTTP requests on that co
Source: GitHub Advisory Database
Ask AI about this articleBeta
The AI only has access to this article — it won't make up facts. Try:
Supporting evidence0 items
Community check0 comments
No votes yet
0% real0% fake