Medium severity · published Oct 28, 2026
CVE-2026-118657
Echo: HTTPS Redirect and HSTS Bypass via Unconditional Trust of Forwarded Scheme Headers
New
5.9
CVSS
–
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Confidentiality
High
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
EC
echo · labstack
>= 5.0.0, < 5.4.0; < 4.16.0 · source: vendor
Affected product
EC
echo
labstack
More from echo
9.6
CVE-2022-40083
Labstack Echo v4.8.0 was discovered to contain an open redirect vulnerability via the Static Handler component
9.1
CVE-2026-118264
Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls
8.2
CVE-2026-118262
Echo: WebSocket proxy can retain connections and handlers after client disconnect
8.2
CVE-2026-118261
Echo: Decompress permits unbounded gzip expansion in v4
8.2
CVE-2026-118260
Echo: BodyDump captures request and response bodies without size limits in v4