CVE-2026-118265 json
Echo: X-Real-IP extractor trusts the header value instead of the sending peer
published 2026-10-23 16 d ago modified 2026-11-05 3 d ago also GHSA-h53f-rm2w-w7rg , GO-2026-6841 , EUVD-2026-112397
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
Echo is a Go web framework. From 5.0.0 until 5.4.1, Echo v5's ExtractIPFromRealIPHeader validates whether the client-supplied X-Real-IP value belongs to a trusted range instead of validating the direct network peer. A client reaching Echo directly, or through a proxy that preserves the header, can supply a loopback or private address and have Context.RealIP return that spoofed identity. Applications using the extractor for IP allowlists, rate limiting, audit logs, or forwarding headers can consequently trust an attacker-controlled address; the default direct extractor and Echo v4 are unaffected. This issue is fixed in 5.4.1.
Patch / fix
- go github.com/labstack/echo/v5 5.4.1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-118265 updated cvss 5.3
github.com/labstack/echo: Echo: IP address spoofing via improper X-Real-IP header validation
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 10 d ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/labstack/echo/v5 | >=5.0.0, <5.4.1 |
5.4.1 |
Affected products
- labstack echo
Classification
- Weakness
-
- CWE-348 Use of Less Trusted Source
References
- github.com /labstack/echo/commit/1855061e572ae9dab727c811d8382f266bfbaae
-
github.com
/labstack/echo/commit/1855061e572ae9dab727c811d8382f266bfbaaec
web, patch
-
github.com
/labstack/echo/security/advisories/GHSA-h53f-rm2w-w7rg
web, advisory
-
github.com
/labstack/echo/releases/tag/v5.4.1
web
-
github.com
/labstack/echo
package
Sources
- CVE List CVE-2026-118265
- GitHub Advisory GHSA-h53f-rm2w-w7rg
- NVD CVE-2026-118265
- OSV GO-2026-6841
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.