Echo has a Static Middleware Double-Unescape Path Traversal
Published 28 Oct 2026 · Updated 5 Nov 2026
Is your project on an affected github.com/labstack/echo/v5?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <5.2.0
- Fixed in
- 5.2.0
go get github.com/labstack/echo/v5@v5.2.0- Affected
- <4.15.3
- Fixed in
- 4.15.3
go get github.com/labstack/echo/v4@v4.15.3Details
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:
// 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
// AFTER (fixed) pathUnescape := false
The commit's test TestStatic_percentEncodedTraversalIsBlocked 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.
Is GHSA-xwq5-6cqp-vx96 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/labstack/echo/v5, and gives you the command that fixes it.
More advisories for github.com/labstack/echo/v5
- LowCVE-2026-118653Rate Limiter Bypass via Spoofed X-Forwarded-For Header in Default Configuration in github.com/labstack/echo · 5 Nov 2026
- LowCVE-2026-118650URL-encoded path bypasses route/group middleware guarding a statically-served path in github.com/labstack/echo · 5 Nov 2026
- LowCVE-2026-118651Reverse Proxy Forwards Attacker-Supplied X-Real-IP to Upstream by Default in github.com/labstack/echo · 5 Nov 2026
- LowCVE-2026-118652Cross-Site Scripting (XSS) via unsanitized JSONP callback in github.com/labstack/echo · 5 Nov 2026
- LowCVE-2026-118266Echo has CSRF Protection Bypass via MethodOverride Rewriting POST to Safe Method in github.com/labstack/echo · 5 Nov 2026
- LowCVE-2026-118658Arbitrary Scheme Injection in WWWRedirect/NonWWWRedirect Middlewares via X-Forwarded-Proto in github.com/labstack/echo · 5 Nov 2026
References
- Linkgithub.com/labstack/echo/security/advisories/GHSA-xwq5-6cqp-vx96
- Linkgithub.com/labstack/echo/issues/2599
- Linkgithub.com/labstack/echo/pull/3006
- Linkgithub.com/labstack/echo/commit/a9ede66a5a7196411131beb1ee801e75bbaf7ac6
- Linkgithub.com/labstack/echo/commit/c3fa2a27ff92b2b8db360de614f999ef1da24725
- Packagegithub.com/labstack/echo
- Linkgithub.com/labstack/echo/releases/tag/v4.15.3
- Linkgithub.com/labstack/echo/releases/tag/v5.2.0
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.