HTTP Request Smuggling Affecting golang-github-labstack-echo package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.43% (38th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-GOLANGGITHUBLABSTACKECHO-21816883
  • published29 Oct 2026
  • disclosed28 Oct 2026

Introduced: 28 Oct 2026

NewCVE-2026-118264  (opens in a new tab)
CWE-444  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest golang-github-labstack-echo.

NVD Description

Note: Versions mentioned in the description apply only to the upstream golang-github-labstack-echo package and not the golang-github-labstack-echo package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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.