CVE-2026-118264

Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls

Published Oct 28, 2026 CVSS 4.0 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
Echo is a Go web framework. From 4.0.0 until 4.16.1 and 5.4.1, Echo's Proxy middleware selects a raw tunnel from a client WebSocket upgrade request before verifying that the configured upstream accepted the upgrade. If the upstream rejects the upgrade with an ordinary keep-alive response, later HTTP requests on the connection are sent directly to that upstream without passing through Echo's router or route-specific middleware. This can bypass authentication or authorization enforced only by Echo routes, but requires an accessible proxy route, a cooperating rejected-upgrade response, and a target without independent upstream authorization. This issue is fixed in 4.16.1 and 5.4.1.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the Echo patch to version 4.16.1 or 5.4.1 or later. The update corrects the CWE‑444 and CWE‑863 weaknesses by validating the proxy upgrade before forwarding requests to upstream services, restoring route‑level access controls.
  • If upgrading is infeasible, immediately remove or disable the Proxy middleware on any routes that rely on Echo for authentication or authorization, thereby mitigating the CWE‑444 and CWE‑863 risks by preventing unauthorized requests from bypassing the router.
  • Configure your upstream services to enforce authentication and authorization independently. By performing these checks at the service level, the CWE‑863 risk of inconsistent authorization is mitigated even if a raw tunnel is created.

Generated by OpenCVE AI on October 28, 2026 at 20:57 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-cxf3-9h37-7rr8 Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Labstack
Labstack echo
Vendors & Products Labstack
Labstack echo
Type Values Removed Values Added
Description Echo is a Go web framework. From 4.0.0 until 4.16.1 and 5.4.1, Echo's Proxy middleware selects a raw tunnel from a client WebSocket upgrade request before verifying that the configured upstream accepted the upgrade. If the upstream rejects the upgrade with an ordinary keep-alive response, later HTTP requests on the connection are sent directly to that upstream without passing through Echo's router or route-specific middleware. This can bypass authentication or authorization enforced only by Echo routes, but requires an accessible proxy route, a cooperating rejected-upgrade response, and a target without independent upstream authorization. This issue is fixed in 4.16.1 and 5.4.1.
Title Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls
Weaknesses CWE-444
CWE-863
References
Metrics cvssV4_0

{'score': 9.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-444

    Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 7:21 PM
Reserved
Oct 27, 2026, 8:13 PM
Status
Undergoing Analysis
Published
Oct 28, 2026, 7:17 PM
Modified
Nov 4, 2026, 11:10 PM
Severity
Moderate
Public date
Oct 28, 2026, 7:03 PM