Vulnerability in Labstack Echo
CVE-2026-118657
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.
Published .
CVSS v3 metric
CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Labstack Echo — versions < 4.16.0, >= 5.0.0, < 5.4.0
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-118657?
- CVE-2026-118657 is a medium-severity vulnerability in Labstack Echo, classified under Origin Validation Error. CVSS score: 5.9/10. Published 2026-10-28.
- How severe is CVE-2026-118657?
- Medium severity. CVSS v3 base score is 5.9 out of 10.