CVE-2026-118655: Echo has a Static Middleware Double-Unescape Path Traversal
Summary
Commit a9ede66a (PR #3006, issue #2599) silently fixed a path traversal vulnerability in the Echo web framework's static file middleware.
Vulnerability
The static middleware double-unescaped URL paths. Go's net/http already decodes Request.URL.Path, but middleware/static.go unconditionally called url.PathUnescape() again:
go // BEFORE (vulnerable) pathUnescape := true
This reassembled path traversal sequences from double-encoded input. An attacker could send GET /%2e%2e%2fsecret.txt or /..%252fsecret.txt and the double-unescape would produce ../secret.txt.
Fix go // AFTER (fixed) pathUnescape := false
The commit's test TestStaticpercentEncodedTraversalIsBlocked explicitly verifies traversal vectors are blocked.
Impact Arbitrary file read from server filesystem via percent-encoded path traversal.
References - Fix: https://github.com/labstack/echo/commit/a9ede66a - Issue: https://github.com/labstack/echo/issues/2599 - PR: https://github.com/labstack/echo/pull/3006
Patches
Fixed in github.com/labstack/echo/v5 v5.2.0 and github.com/labstack/echo/v4 v4.15.3, where the Static middleware stopped unescaping an already decoded path. Maintainer analysis: reading files outside the configured root could not be reproduced; the confirmed impact was that a double-encoded slash (%252F) could reach a file under a guarded route when the Static middleware is registered globally. Upgrade to v5.4.0 / v4.16.0 or later, which also includes related fixes for encoded and dot-segment paths.
Workarounds
Keep files that need protection outside the Static middleware's root directory.
Other sources
Echo has a Static Middleware Double-Unescape Path Traversal in github.com/labstack/echo
— OSV
Echo is a Go web framework. Prior to 4.15.3 and 5.2.0, middleware.Static can decode an already decoded Request.URL.Path a second time. Double-encoded separators can consequently be reconstructed before filesystem resolution. This can reach a file under a guarded route when the static middleware is registered globally. This issue is fixed in 4.15.3 and 5.2.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/labstack/echo/v4to a version that resolves this vulnerability.Fixed in 4.15.3 - Upgrade
Upgrade
go/github.com/labstack/echo/v5to a version that resolves this vulnerability.Fixed in 5.2.0 - Upgrade
Upgrade
github.com/labstack/echo/v5to a version that resolves this vulnerability.Fixed in v5.4.0 - Upgrade
Upgrade
github.com/labstack/echo/v4to a version that resolves this vulnerability.Fixed in v4.16.0 - Compensating control
Keep files that need protection outside the Static middleware's root directory.
Event History
Frequently Asked Questions
Which deployments are exposed?
Deployments using Echo before 4.15.3 or 5.2.0 are exposed when middleware.Static is registered globally and a guarded route can be reached through static-file resolution.
What does an attacker need to exploit this?
The attacker can send a network request without authentication or user interaction, but must craft a request using double-encoded path separators so that a second decode reconstructs separators before filesystem resolution. The high attack complexity reflects the required request-path conditions.
What should be done if upgrading is not immediately possible?
The provided information identifies upgrading to Echo 4.15.3 or 5.2.0 as the fix. It does not provide a documented temporary mitigation.