CVE-2026-118653

Echo: Rate Limiter Bypass via Spoofed X-Forwarded-For Header in Default Configuration

Published Oct 28, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability allows a remote attacker to bypass rate limiting by altering the X-Forwarded-For header. Echo's context delivers a client IP that comes from the header when no IP extractor is configured, and the default rate limiter uses that IP as a bucket identifier. By rotating arbitrary forwarded-address values, an attacker can generate additional buckets and slip past IP-based throttling intended for brute‑force or request‑volume protection. The weakness is a misuse of client‑supplied data for authentication purposes, classified as CWE‑290, and the use of an untrusted proxy header for client identification, classified as CWE‑807.

Affected Systems

Affected deployments are those running labstack Echo version 4.0.0 through 5.0.x. The production applications that rely on the default configuration for IP extraction and rate limiting are impacted, while versions before 4.0.0 or after 5.1.0 have the fix applied.

Risk and Exploitability

The CVSS score of 5.3 places the issue in the medium severity range. Exploitation requires only the ability to send HTTP requests with a custom X-Forwarded-For header, which is possible from any remote client; the EPSS score of 0.00415 indicates a very low exploitation probability, and the vulnerability is not yet listed in CISA's KEV catalog. The attack would grant the attacker access to unthrottled request rates, enabling brute‑force attempts against authentication endpoints or denial‑of‑service through traffic amplification. While no privileged access or code execution is required, the ability to bypass security controls represents a tangible risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Echo to version 5.1.0 or later.
  • Configure Echo.IPExtractor to use a trusted extractor so that the real client IP comes from a secure source rather than the X-Forwarded-For header.
  • If an immediate upgrade is not possible, remove or temporarily disable the IP‑based rate limiter, or reconfigure it to use a stronger client identifier.

Generated by OpenCVE AI on November 6, 2026 at 02:10 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-246p-cpwv-v3jq Echo has Rate Limiter Bypass via Spoofed X-Forwarded-For Header in Default Configuration
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Labstack
Labstack echo
Vendors & Products Labstack
Labstack echo
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

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-290

    Authentication Bypass by Spoofing

  • CWE-807

    Reliance on Untrusted Inputs in a Security Decision

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 2, 2026, 8:41 PM
Reserved
Oct 28, 2026, 5:25 PM
Status
Undergoing Analysis
Published
Oct 28, 2026, 8:17 PM
Modified
Nov 2, 2026, 9:17 PM
Severity
Moderate
Public date
Oct 28, 2026, 7:42 PM