Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

CVSS 4.0 9.1 CRITICALCheck source for fixed versionsKEV status unknown

Historical advisory recorded 28 Oct 2026 19:46:48 UTC. Read the latest advisory.

cve-program · CVE-2026-118264

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-118264

Published

echo

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "labstack",
                    "product": "echo",
                    "versions": [
                        {
                            "version": ">= 4.0.0, < 4.16.1",
                            "status": "affected"
                        },
                        {
                            "version": ">= 5.0.0, < 5.4.1",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 17 Nov 12:19 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current