CVSS 3.1
5.9 mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:NMedium (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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:Ngithub.com/labstack/echo/v5 (Go): fixed in 5.4.0github.com/labstack/echo/v4 (Go): fixed in 4.16.0Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| labstack echo | >= 5.0.0, < 5.4.0 |
| labstack echo | < 4.16.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-2ffq-g2xg-c22p | Go | github.com/labstack/echo/v5 | <5.4.0 | 5.4.0 |
| GHSA-2ffq-g2xg-c22p | Go | github.com/labstack/echo/v4 | <4.16.0 | 4.16.0 |
| GO-2026-6879 | Go | github.com/labstack/echo/v4 | <4.16.0 | 4.16.0 |
| GO-2026-6879 | Go | github.com/labstack/echo/v5 | <5.4.0 | 5.4.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | golang-github-labstack-echo | no fix listed | DEBIAN-CVE-2026-118657 |
| Ubuntu | 20.04:LTS | golang-github-labstack-echo.v2, golang-github-labstack-echo.v3 | no fix listed | UBUNTU-CVE-2026-118657 |
| Ubuntu | 22.04:LTS | golang-github-labstack-echo, golang-github-labstack-echo.v2, golang-github-labstack-echo.v3 | no fix listed | UBUNTU-CVE-2026-118657 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 | golang-github-labstack-echo | no fix listed | UBUNTU-CVE-2026-118657 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | govulncheck-vulndb | 0.0.20261105T234957-160000.1.1 | SUSE-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 rates this Moderate.
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.
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).