cve.bz

CVE-2026-118657 labstack echo: Origin Validation Error

5.9 mediumEPSS 0.1%Fix available

Medium (5.9) in labstack echo. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/labstack/echo/v5 5.4.0.

On this page
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.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 3rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-346 Origin Validation Error
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-118657 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118657?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118657?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118657 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
labstack echo>= 5.0.0, < 5.4.0
labstack echo< 4.16.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2ffq-g2xg-c22pGogithub.com/labstack/echo/v5<5.4.05.4.0
GHSA-2ffq-g2xg-c22pGogithub.com/labstack/echo/v4<4.16.04.16.0
GO-2026-6879Gogithub.com/labstack/echo/v4<4.16.04.16.0
GO-2026-6879Gogithub.com/labstack/echo/v5<5.4.05.4.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14golang-github-labstack-echono fix listedDEBIAN-CVE-2026-118657
Ubuntu20.04:LTSgolang-github-labstack-echo.v2, golang-github-labstack-echo.v3no fix listedUBUNTU-CVE-2026-118657
Ubuntu22.04:LTSgolang-github-labstack-echo, golang-github-labstack-echo.v2, golang-github-labstack-echo.v3no fix listedUBUNTU-CVE-2026-118657
Ubuntu24.04:LTS, 26.04:LTS, 26.10golang-github-labstack-echono fix listedUBUNTU-CVE-2026-118657
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0govulncheck-vulndb0.0.20261105T234957-160000.1.1SUSE-SU-2026:24730-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is evaluated as having Moderate impact because bypassing transport security enforcement requires specific network exposure—such as direct, unprotected HTTP ingress or an edge proxy that fails to sanitize client headers—and successful exploitation does not directly expose application state or grant unauthorized remote access. In standard enterprise deployments, applications built with the Echo framework are positioned behind reverse proxies or ingress controllers that overwrite client-supplied forwarding headers, significantly limiting practical attack vectors. However, if an attacker can send unsanitized forwarded scheme headers directly to an unencrypted backend, they can prevent automated HTTPS redirection or suppress HSTS headers, thereby lowering transport security protections for downstream clients.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-118657.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-346 (16).

References

Check your stackJSON