Is CVE-2026-118650 exploited in the wild?

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

How severe is CVE-2026-118650?

High severity, with a CVSS score of 7.5, published 28 October 2026.

Which products and versions are affected?

github.com/labstack/echo/v4 (Go) < 4.16.0, SEMVER:introduced=0,fixed=4.16.0; github.com/labstack/echo/v5 (Go) < 5.4.0, SEMVER:introduced=0,fixed=5.4.0, SEMVER:introduced=5.0.0,fixed=5.4.0; Labstack Echo before 4.16.0 and before 5.4.0.

Is there a fix for CVE-2026-118650?

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

How is CVE-2026-118650 attacked?

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

Am I affected by CVE-2026-118650?

Check whether you run github.com/labstack/echo/v4 (Go), 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-118650: Echo path traversal via encoded static file requests

Q: Is there a fix for CVE-2026-118650?

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

Q: How is CVE-2026-118650 attacked?

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

Q: Am I affected by CVE-2026-118650?

Check whether you run github.com/labstack/echo/v4 (Go), 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-118650 · Severity: high · CVSS 7.5 · Published 2026-10-28

Echo is a Go web framework used to build HTTP APIs and web services. A flaw in its static file middleware allows attackers to access files outside the intended static directory by sending specially encoded request paths, bypassing route-based access controls. This could expose sensitive files or configuration data served by the application.

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

Quick answers

Is CVE-2026-118650 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-118650 being exploited in the wild.
How severe is CVE-2026-118650?: High severity, with a CVSS score of 7.5, published 28 October 2026.
Which products and versions are affected?: github.com/labstack/echo/v4 (Go) < 4.16.0, SEMVER:introduced=0,fixed=4.16.0; github.com/labstack/echo/v5 (Go) < 5.4.0, SEMVER:introduced=0,fixed=5.4.0, SEMVER:introduced=5.0.0,fixed=5.4.0; Labstack Echo before 4.16.0 and before 5.4.0.
Is there a fix for CVE-2026-118650?: Yes. github.com/labstack/echo/v4 (Go): upgrade to 4.16.0 or later; github.com/labstack/echo/v5 (Go): upgrade to 5.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-118650 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-118650?: Check whether you run github.com/labstack/echo/v4 (Go), 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/v4 (Go): upgrade to 4.16.0 or later
```
go get github.com/labstack/echo/v4@v4.16.0
```
github.com/labstack/echo/v5 (Go): upgrade to 5.4.0 or later
```
go get github.com/labstack/echo/v5@v5.4.0
```

Technical details

The Static middleware interprets percent-encoded and Unicode-normalized request paths differently than Echo's router: the router matches the raw encoded path while the static handler decodes it before file resolution. An attacker can use encoded slashes (%2F) or other encodings to traverse the file system and access files that would be blocked if accessed directly. The fix ensures the static middleware resolves files from the same path representation the router matched.

Affected products

labstack Echo before 4.16.0 and before 5.4.0

Identifiers

CVE-2026-118650
GHSA-375p-5qhx-8wq4
GO-2026-6873

Timeline

2026-10-28: disclosed
2026-09-27: patched

References

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