Technical impact
Echo’s Proxy middleware opens a raw tunnel for a client WebSocket upgrade before confirming that the upstream server has accepted the upgrade. If the upstream rejects the upgrade with a normal keep‑alive response, the proxy subsequently forwards all HTTP requests on that connection directly to the upstream without routing them through Echo’s router or any route‑specific middleware. This flaw allows an attacker to bypass authentication or authorization checks that are enforced only by Echo routes, potentially exposing protected data or enabling privileged actions.
Affected Systems
The vulnerability affects the Echo framework by labstack. Versions from 4.0.0 up to, but not including, 4.16.1 are vulnerable. The 5.x series is also affected for releases earlier than 5.4.1; it is inferred that all 5.0.0 through 5.4.1‑1 versions are susceptible because the fix was introduced in 5.4.1.
Risk and Exploitability
The CVSS score of 9.1 indicates a high severity, and the EPSS score is not available, but the lack of KEV listing does not lessen the risk. Exploitation requires a proxy route, an upstream server that cooperatively sends a plain keep‑alive rejection, and the absence of independent upstream authorization. While the technical prerequisites are non‑trivial, the impact is severe; the likely attack vector is a crafted WebSocket upgrade request to a vulnerable proxy endpoint. It is inferred that prior releases in the 5.x series were vulnerable because the fix was only applied in 5.4.1.
Github GHSA