Bug 2563120 (CVE-2026-118264) - CVE-2026-118264 github.com/labstack/echo: Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls
Summary: CVE-2026-118264 github.com/labstack/echo: Echo: Rejected WebSocket upgrades c...
Keywords:
Status: NEW
Alias: CVE-2026-118264
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2567384 2567385 2567386 2567387 2567388 2567389
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-28 19:23 UTC by OSIDB Bzimport
Modified: 2026-11-05 19:50 UTC (History)
41 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-28 19:23:42 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.