CVE-2026-25766: Echo has a Windows path traversal via backslash in middleware.Static default filesystem
Summary On Windows, Echo’s middleware.Static using the default filesystem allows path traversal via backslashes, enabling unauthenticated remote file read outside the static root.
Details
In middleware/static.go, the requested path is unescaped and normalized with path.Clean (URL semantics). path.Clean does not treat \ as a path separator, so ..\ sequences remain in the cleaned path. The resulting path is then passed to currentFS.Open(...). When the filesystem is left at the default (nil), Echo uses defaultFS which calls os.Open (echo.go:792). On Windows, os.Open treats \ as a path separator and resolves ..\, allowing traversal outside the static root.
Relevant code: - middleware/static.go (path unescape + path.Clean + currentFS.Open) - echo.go defaultFS.Open → os.Open
This is the same class as CVE-2020-36565 (fixed in v4 by switching to OS-aware cleaning), but in v5 the path.Clean + defaultFS combination reintroduces the Windows backslash traversal.
PoC Windows only.
Sample code (main.go): go package main
import ( "log" "net/http"
"github.com/labstack/echo/v5" "github.com/labstack/echo/v5/middleware" )
func main() { e := echo.New()
// Important: use middleware.Static with default filesystem (nil) e.Use(middleware.Static("public"))
e.GET("/healthz", func(c echo.Context) error { return c.String(http.StatusOK, "ok") })
addr := ":1323" log.Printf("listening on %s", addr) if err := e.Start(addr); err != nil && err != http.ErrServerClosed { log.Fatal(err) } } Static file:
public/index.html
(content can be any HTML)
Run: go run .
Verify:
curl http://localhost:1323/index.html curl --path-as-is "http://localhost:1323/..%5c..%5cWindows%5cSystem32%5cdrivers%5cetc%5chosts" Expected: 404
Screenshot: <img width="884" height="689" alt="image" src="https://github.com/user-attachments/assets/acb14d70-2a43-47c1-8927-2f3da491a853" /> <img width="1022" height="162" alt="image" src="https://github.com/user-attachments/assets/f2b92aa2-541e-461d-81a2-8a5907d7a447" />
### Impact Path traversal leading to arbitrary file read outside the static root. Any unauthenticated remote user can read local files that the Echo process has access to on Windows, if middleware.Static is used with the default filesystem.
Other sources
Echo is a Go web framework. In versions 5.0.0 through 5.0.2 on Windows, Echo’s middleware.Static using the default filesystem allows path traversal via backslashes, enabling unauthenticated remote file read outside the static root. In middleware/static.go, the requested path is unescaped and normalized with path.Clean (URL semantics). path.Clean does not treat \ as a path separator, so ..\ sequences remain in the cleaned path. The resulting path is then passed to currentFS.Open(...). When the filesystem is left at the default (nil), Echo uses defaultFS which calls os.Open (echo.go:792). On Windows, os.Open treats \ as a path separator and resolves ..\, allowing traversal outside the static root. Version 5.0.3 fixes the issue.
— NVD
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2026-25766?
CVE-2026-25766 is classified as a high severity vulnerability due to its ability to allow unauthenticated remote file reads.
How do I fix CVE-2026-25766?
To fix CVE-2026-25766, upgrade to the latest version of the Echo framework, specifically version 5.0.3 or later.
What types of attacks can CVE-2026-25766 facilitate?
CVE-2026-25766 can facilitate path traversal attacks, allowing unauthorized access to files outside the designated static root.
Which versions of the Echo framework are affected by CVE-2026-25766?
CVE-2026-25766 affects Echo version 5.0.0 through 5.0.2.
Is authentication required to exploit CVE-2026-25766?
No, CVE-2026-25766 can be exploited without authentication as it allows unauthenticated access.