Origin Validation Error Affecting golang-github-labstack-echo package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.13% (3rd 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-21816891
  • published29 Oct 2026
  • disclosed28 Oct 2026

Introduced: 28 Oct 2026

NewCVE-2026-118657  (opens in a new tab)
CWE-346  (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. Prior to 4.16.0 and 5.4.0, Context.Scheme unconditionally trusts forwarded scheme headers from any client. A client that reaches Echo directly over plaintext HTTP can claim an HTTPS scheme and bypass HTTPSRedirect because the request is treated as already secure. Separately, behind a TLS-terminating proxy that passes an attacker-controlled header, a claimed HTTP scheme can suppress the Strict-Transport-Security header even though the browser receives the response over HTTPS. The practical risk is reduced when a trusted proxy overwrites the headers and direct backend access is prevented, but the framework previously had no trusted-source configuration for this decision. This issue is fixed in 4.16.0 and 5.4.0.