Answer in brief
CVE-2026-118657 records a Medium severity (CVSS 5.9) vulnerability in Echo: HTTPS Redirect and HSTS Bypass via Unconditional Trust of Forwarded Scheme Headers. The current sources do not mark it as known exploited. The current feed maps labstack/echo (generic), github.com/labstack/echo/v4 (go), github.com/labstack/echo/v5 (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps labstack/echo (generic), github.com/labstack/echo/v4 (go), github.com/labstack/echo/v5 (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| labstack/echogeneric | >=5.0.0 <5.4.0 || <4.16.0 | 4.16.0, 5.4.0 |
| github.com/labstack/echo/v4go | <4.16.0 | 4.16.0 |
| github.com/labstack/echo/v5go | <5.4.0 | 5.4.0 |
Published upstream
Oct 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 28, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 28, 2026
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.
Quoted source text, attributed separately from HOL analysis.