Is CVE-2026-118265 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-118265 being exploited in the wild.

How severe is CVE-2026-118265?

Medium severity, with a CVSS score of 5.3, published 28 October 2026.

Which products and versions are affected?

github.com/labstack/echo/v5 (Go) SEMVER:introduced=5.0.0,fixed=5.4.1; Labstack Echo 5.0.0 to 5.4.0.

Is there a fix for CVE-2026-118265?

Yes. github.com/labstack/echo/v5 (Go): upgrade to 5.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-118265 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-118265?

Check whether you run github.com/labstack/echo/v5 (Go) or Labstack Echo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-118265: Echo X-Real-IP header spoofing via untrusted extractor

CVE-2026-118265 · Severity: medium · CVSS 5.3 · Published 2026-10-28

Echo is a Go web framework used to build server applications. Echo v5's ExtractIPFromRealIPHeader function improperly validates the X-Real-IP header, allowing clients to spoof their IP address. Applications using this extractor for IP-based decisions—such as allowlists, rate limiting, or audit logging—can be tricked into trusting an attacker's falsified address, potentially granting unauthorized access or bypassing security controls.

Technologies: github.com/labstack/echo/v5 (Go), Labstack Echo. Vendors: Go, Labstack.

Quick answers

Is CVE-2026-118265 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-118265 being exploited in the wild.
How severe is CVE-2026-118265?: Medium severity, with a CVSS score of 5.3, published 28 October 2026.
Which products and versions are affected?: github.com/labstack/echo/v5 (Go) SEMVER:introduced=5.0.0,fixed=5.4.1; Labstack Echo 5.0.0 to 5.4.0.
Is there a fix for CVE-2026-118265?: Yes. github.com/labstack/echo/v5 (Go): upgrade to 5.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-118265 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-118265?: Check whether you run github.com/labstack/echo/v5 (Go) or Labstack Echo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/labstack/echo/v5 (Go): upgrade to 5.4.1 or later
```
go get github.com/labstack/echo/v5@v5.4.1
```

Technical details

The ExtractIPFromRealIPHeader extractor in Echo v5.0.0–5.4.0 validates whether a client-supplied X-Real-IP header value belongs to a trusted range, but fails to first verify that the direct network peer is itself trusted. An attacker connecting directly or through a proxy that preserves the header can inject a loopback or private address, causing Context.RealIP() to return the spoofed identity. The default direct extractor and Echo v4 are unaffected.

Affected products

labstack Echo 5.0.0 to 5.4.0

Identifiers

CVE-2026-118265
GHSA-h53f-rm2w-w7rg
GO-2026-6841

Timeline

2026-10-28: disclosed
2026-10-22: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.