CVE-2026-25766 json
Echo has a Windows path traversal via backslash in middleware.Static default filesystem
published 2026-02-17 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-8207 , GHSA-pgvm-wxw2-hrv9 , GO-2026-4502
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/labstack/echo/v5 5.0.3
- labstack echo 5.0.3
- govulncheck-vulndb openSUSE Leap 15.6 0.0.20260226T182644-150000.1.149.1
suse advisories SUSE-SU-2026:0757-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
- github.com/labstack/echo@b1d4430 commit
- github.com/labstack/echo#2891 pull request
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/labstack/echo/security/advisories/GHSA-pgvm-wxw2-hrv9 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/labstack/echo/v5 | >=5.0.0, <5.0.3 |
5.0.3 |
Affected products
- labstack echo
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/labstack/echo/pull/2891
web, issue-tracking, patch
-
github.com
/labstack/echo/commit/b1d443086ea27cf51345ec72a71e9b7e9d9ce5f1
web, patch
-
github.com
/labstack/echo/security/advisories/GHSA-pgvm-wxw2-hrv9
web, exploit, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-25766
advisory
-
github.com
/labstack/echo
package
-
pkg.go.dev
/vuln/GO-2026-4502
web
Sources
- CVE List CVE-2026-25766
- GitHub Advisory GHSA-pgvm-wxw2-hrv9
- NVD CVE-2026-25766
- OSV GO-2026-4502
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.