Advisory record · GHSA-246p-cpwv-v3jq

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

CVSS 5.3 MediumEPSS 0.0042 · 36th percentile

Published by the GitHub Advisory Database at 28 Oct 2026, 19:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/labstack/echo/v5Go<5.1.05.1.0
github.com/labstack/echo/v4Go>=4.0.0, <=4.16.2No fixed version yet
Identifiers
GHSA-246p-cpwv-v3jq · CVE-2026-118653 · GO-2026-6872
Weakness (CWE)
CWE-290
Published
28 Oct 2026
Updated
5 Nov 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Echo v5 versions before 5.1.0 and Echo v4 versions 4.0.0 through 4.16.2 are affected. When IPExtractor is left unset, RealIP() trusts the client-supplied X-Forwarded-For header, so a remote attacker can rotate that header to get a fresh rate-limit bucket per request and bypass the default RateLimiter middleware. Upgrade echo v5 to 5.1.0 or later; no fixed version is listed for echo v4. Workaround: configure IPExtractor for your deployment, or set the rate limiter's IdentifierExtractor to a value clients cannot choose.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0042, the 36th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 28 Oct 2026, 19:42 UTC Confirmed by the CVE List
  2. 28 Oct 2026, 20:17 UTC Confirmed by NVD
  3. 31 Oct 2026, 14:11 UTC First seen by agentprime
  4. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.