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 CRITICALEUVD CVSS 4.0 9.1 CVSS 4.0 · [email protected] · Secondary 9.1 CRITICALCVSS_V4 Publisher rating CRITICALFixed by github.com/labstack/echo/v4 4.16.1Fixed by github.com/labstack/echo/v5 5.4.1osv · severity unknownFixed by github.com/labstack/echo/v4 4.16.1Fixed by github.com/labstack/echo/v5 5.4.1KEV status unknown

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

euvd · EUVD-2026-112396

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

nvd · 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

osv · GHSA-cxf3-9h37-7rr8

Published

## 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 connection were forwarded directly to the same upstream without passing through Echo's router or route-specific middleware. This can bypass authentication or authorization enforced only at Echo's routes. Exploitation requires an accessible proxy route, an upstream that rejects the upgrade without closing the connection, and a target resource on that upstream without independent authorization. The issue does not provide arbitrary-host proxying or bypass the upstream's own authentication. ## Affected versions and patch The raw proxy implementation is present throughout the v4 and v5 release lines up to v4.16.0 and v5.4.0. Runtime reproductions confirmed v4.15.0, v4.16.0, v5.0.0 and v5.4.0; source history also shows the missing upgrade-response validation in v4.0.0. Upgrade to [v4.16.1](https://github.com/labstack/echo/releases/tag/v4.16.1) or [v5.4.1](https://github.com/labstack/echo/releases/tag/v5.4.1). The patch routes WebSocket upgrades through Go's HTTP reverse proxy and enters a tunnel only after a valid upstream upgrade response. Rejected upgrades remain ordinary HTTP requests. Fix commits: [v4](https://github.com/labstack/echo/commit/3fb0ba7e17645bb65611e2a08875d0a2f65c421f), [v5](https://github.com/labstack/echo/commit/1855061e572ae9dab727c811d8382f266bfbaaec). ## Workarounds Reject WebSocket upgrade requests before they reach affected Echo proxy routes, or enforce authorization independently at every upstream resource. Merely returning a non-101 response from the upstream does not prevent the vulnerable raw tunnel. ## Credits Reported by @Duodum.

Read the publisher's advisory

osv · GO-2026-6839

Published

Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls in github.com/labstack/echo

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

euvd · EUVD-2026-112396

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Oct 28, 2026, 7:03:01 PM

dateUpdated: Oct 30, 2026, 7:21:07 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

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

nvd · CVE-2026-118264

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Undergoing Analysis

Weakness classifications: CWE-444 · CWE-863

Original publisher date fields

published: 2026-10-28T19:17:31.237

lastModified: 2026-11-04T23:10:00.223

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

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

osv · GHSA-cxf3-9h37-7rr8

Published

github.com/labstack/echo/v4

Go

SEMVER · introduced 4.0.0 → fixed 4.16.1

github.com/labstack/echo/v5

Go

SEMVER · introduced 5.0.0 → fixed 5.4.1

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

osv · GO-2026-6839

Published

github.com/labstack/echo/v4

Go

SEMVER · introduced 4.0.0 → fixed 4.16.1

github.com/labstack/echo/v5

Go

SEMVER · introduced 5.0.0 → fixed 5.4.1

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 16 Nov 06:51 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current