CVSS 3.1
5.3 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NMedium (5.3) in labstack echo. EPSS 0.2% 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:L/PR:N/UI:N/S:U/C:N/I:L/A:Ngithub.com/labstack/echo/v5 (Go): fixed in 5.4.0Explain CVE-2026-118651 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118651?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118651?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-118651 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 | >= 4.0.0, < 5.4.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-99jh-6h7p-pp36 | Go | github.com/labstack/echo/v5 | <5.4.0 | 5.4.0 |
| GHSA-99jh-6h7p-pp36 | Go | github.com/labstack/echo/v4 | >=4.0.0 <=4.16.2 | no fix published |
| GO-2026-6875 | Go | github.com/labstack/echo/v4 | >=4.0.0 | no fix published |
| GO-2026-6875 | 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-118651 |
| Ubuntu | 20.04:LTS | golang-github-labstack-echo.v2, golang-github-labstack-echo.v3 | no fix listed | UBUNTU-CVE-2026-118651 |
| Ubuntu | 22.04:LTS | golang-github-labstack-echo, golang-github-labstack-echo.v2, golang-github-labstack-echo.v3 | no fix listed | UBUNTU-CVE-2026-118651 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 | golang-github-labstack-echo | no fix listed | UBUNTU-CVE-2026-118651 |
| 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 rated as Moderate severity because, while it can be triggered remotely without authentication, successful exploitation is limited to integrity impacts such as spoofing network identities rather than direct system compromise or information leakage. The issue only manifests when applications implement Echo's reverse proxy functionality with default configurations that omit an explicit IP extractor. Furthermore, downstream consequences depend heavily on backend architecture, requiring upstream services to implicitly trust the forwarded client header for policy enforcement, rate restrictions, or audit trails.
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-118651.
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).