Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-h53f-rm2w-w7rg | Echo: X-Real-IP extractor trusts the header value instead of the sending peer |
Wed, 28 Oct 2026 21:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Labstack
Labstack echo |
|
| Vendors & Products |
Labstack
Labstack echo |
Wed, 28 Oct 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Echo: X-Real-IP extractor trusts the header value instead of the sending peer | |
| Weaknesses | CWE-348 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-28T19:03:56.934Z
Reserved: 2026-10-27T20:13:55.314Z
Link: CVE-2026-118265
No data.
Status : Received
Published: 2026-10-28T19:17:31.377
Modified: 2026-10-28T19:17:31.377
Link: CVE-2026-118265
No data.
OpenCVE Enrichment
Updated: 2026-10-28T20:45:15Z
Github GHSA