VulnerabilityPublished 28 Oct 2026

CVE-2026-118653: labstack echo · Authentication Bypass by Spoofing

Affects labstack echoSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 5.1.0 when convenient.

Data as of 28 Oct 2026, 20:13 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 5.1.0

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade echo and github.com/labstack/echo to 5.1.0.

Affected software

Product	Affected	Fixed in
labstackecho	Affected >=4.0.0 <5.1.0	Fixed in 5.1.0
Gogithub.com/labstack/echo`pkg:golang/github.com/labstack/echo`Other threats	Affected >=4.0.0 <5.1.0	Fixed in 5.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Echo version 5.1.0 or later, where this issue is fixed. Until then, configuring Echo.IPExtractor to a trusted source or implementing alternative rate-limiting strategies that do not rely solely on client-supplied IP headers can help mitigate the risk.

Description

A vulnerability in the Echo Go web framework versions 4.0.0 through 5.0.x allows remote attackers to bypass IP-based rate limiting. The issue arises because Context.RealIP falls back to client-supplied X-Forwarded-For or X-Real-IP headers when Echo.IPExtractor is unset, enabling attackers to rotate these headers to evade rate limits. This flaw is fixed in Echo version 5.1.0.

Impact

The vulnerability allows remote attackers to bypass IP-based rate limiting by spoofing IP addresses via HTTP headers. This can undermine protections against brute-force attacks or excessive request volumes, potentially leading to increased unauthorized access attempts or denial-of-service conditions. There is no direct confidentiality or availability impact reported, but integrity impact is rated low.

Summary

Echo is a Go web framework where, from versions 4.0.0 until 5.1.0, the Context.RealIP method falls back to using client-supplied X-Forwarded-For or X-Real-IP header values if Echo.IPExtractor is not configured. The default RateLimiter uses the result of Context.RealIP as the client identifier for throttling. An attacker can manipulate these headers to rotate arbitrary forwarded IP addresses, thereby obtaining new rate-limit buckets and bypassing IP-based throttling mechanisms designed to protect against brute-force or excessive request volumes. This authentication bypass by spoofing is classified under CWE-290. The vulnerability is resolved in Echo version 5.1.0.

CWE-290Authentication Bypass by Spoofing (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
OWASP Cheat Sheets
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V3.5.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Web Services API Signature Forgery Leveraging Hash Function Extension Weakness (opens in a new tab)
Signature Spoof (opens in a new tab)
Signature Spoofing by Misrepresentation (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 20:00 UTC

WeaknessesCWE-290

Technical details

References

Community reviews

Related threats