Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-246p-cpwv-v3jq | Echo has Rate Limiter Bypass via Spoofed X-Forwarded-For Header in Default Configuration |
Wed, 28 Oct 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Labstack
Labstack echo |
|
| Vendors & Products |
Labstack
Labstack echo |
Wed, 28 Oct 2026 20:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Echo is a Go web framework. From 4.0.0 until 5.1.0, Context.RealIP falls back to client-supplied X-Forwarded-For or X-Real-IP values when Echo.IPExtractor is unset, and the default RateLimiter uses that result as its client identifier. A remote attacker can rotate arbitrary forwarded-address values to obtain new rate-limit buckets and bypass IP-based throttling used for controls such as brute-force or request-volume protection. This issue is fixed in Echo v5.1.0. | |
| Title | Echo: Rate Limiter Bypass via Spoofed X-Forwarded-For Header in Default Configuration | |
| Weaknesses | CWE-290 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-28T19:42:05.556Z
Reserved: 2026-10-28T17:25:37.561Z
Link: CVE-2026-118653
No data.
Status : Received
Published: 2026-10-28T20:17:22.400
Modified: 2026-10-28T20:17:22.400
Link: CVE-2026-118653
No data.
OpenCVE Enrichment
Updated: 2026-10-28T21:44:52Z
Github GHSA