Is CVE-2026-118655 exploited in the wild?

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

How severe is CVE-2026-118655?

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

Which products and versions are affected?

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

How is CVE-2026-118655 attacked?

It is attacked over the network.

Am I affected by CVE-2026-118655?

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-118655: Echo path traversal via double URL encoding in Static middleware

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

Yes. github.com/labstack/echo/v4 (Go): upgrade to 4.15.3 or later; github.com/labstack/echo/v5 (Go): upgrade to 5.2.0 or later. Until then: Upgrade to Echo 4.15.3, 5.2.0, or later. Alternatively, disable the Static middleware globally or restrict it to specific paths that do not expose sensitive files. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-118655 attacked?

It is attacked over the network.

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

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-118655 · Severity: medium · CVSS 5.9 · Published 2026-10-28

Echo is a Go web framework used to build HTTP services. The Static middleware component can be bypassed by attackers using double-encoded path separators, allowing them to access files outside their intended directory and potentially reach protected resources. This affects Echo versions before 4.15.3 and 5.2.0.

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

Quick answers

Is CVE-2026-118655 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-118655 being exploited in the wild.
How severe is CVE-2026-118655?: Medium severity, with a CVSS score of 5.9, published 28 October 2026.
Which products and versions are affected?: github.com/labstack/echo/v4 (Go) < 4.15.3, SEMVER:introduced=0,fixed=4.15.3; github.com/labstack/echo/v5 (Go) < 5.2.0, SEMVER:introduced=0,fixed=5.2.0; Labstack Echo before 4.15.3 and 5.2.0.
Is there a fix for CVE-2026-118655?: Yes. github.com/labstack/echo/v4 (Go): upgrade to 4.15.3 or later; github.com/labstack/echo/v5 (Go): upgrade to 5.2.0 or later. Until then: Upgrade to Echo 4.15.3, 5.2.0, or later. Alternatively, disable the Static middleware globally or restrict it to specific paths that do not expose sensitive files. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-118655 attacked?: It is attacked over the network.
Am I affected by CVE-2026-118655?: 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.15.3 or later
```
go get github.com/labstack/echo/v4@v4.15.3
```
github.com/labstack/echo/v5 (Go): upgrade to 5.2.0 or later
```
go get github.com/labstack/echo/v5@v5.2.0
```

Upgrade to Echo 4.15.3, 5.2.0, or later. Alternatively, disable the Static middleware globally or restrict it to specific paths that do not expose sensitive files.

Technical details

The vulnerability exists in middleware.Static, which performs a second URL decode on Request.URL.Path that is already decoded by net/http. An attacker can send double-encoded separators (e.g., "%252F" for "/") that survive the initial decode and are reconstructed before filesystem resolution, enabling path traversal. The attack succeeds when the static middleware is registered globally and can bypass route-level access controls.

Affected products

LabStack Echo before 4.15.3 and 5.2.0

Identifiers

CVE-2026-118655
GHSA-xwq5-6cqp-vx96
GO-2026-6885

Timeline

2026-10-28: disclosed
2026-06-14: patched

References

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