Skip to main content
VulnerabilityPublished

CVE-2026-118651: labstack echo · Origin Validation Error

Affects labstack echoSource CVE Database V5

0

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

Data as of 28 Oct 2026, 19:57 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 5.4.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

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

Affected software

ProductAffectedFixed in
labstackechoAffected
  • >=4.0.0 <5.4.0
Fixed in
  • 5.4.0
Gogithub.com/labstack/echopkg:golang/github.com/labstack/echoOther threatsAffected
  • >=4.0.0 <5.4.0
Fixed in
  • 5.4.0

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

AI-suggested

Upgrade Echo to version 5.4.0 or later, where this issue is fixed. Alternatively, configure Echo.IPExtractor properly to prevent the Proxy middleware from forwarding attacker-supplied X-Real-IP headers. No other mitigation is indicated by the vendor advisory.

Description

A vulnerability in the Echo Go web framework versions 4.0.0 up to but not including 5.4.0 allows an attacker to spoof the client IP address forwarded to upstream services via the X-Real-IP header when the Proxy middleware is used without configuring Echo.IPExtractor. This can undermine IP-based access controls, rate limiting, audit logging, or geographic restrictions. The issue is fixed in version 5.4.0.

References

Community reviews

Loading reviews…