CVE-2026-55677: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in labstack echo
Echo is a Go web framework. Prior to 4.15.3 and 5.2.0, Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an attacker to bypass route-level access controls and read static files without authorization. This vulnerability is fixed in 4.15.3 and 5.2.0.
AI Analysis
Technical Summary
In labstack Echo versions before 4.15.3 and 5.2.0, the router matches routes using the raw encoded URL path, preserving encoded slashes (%2F), while the StaticDirectoryHandler unescapes %2F to a slash before resolving filesystem paths. This discrepancy enables an attacker to bypass route-level access controls and access static files without authorization, constituting a path traversal vulnerability (CWE-22). The vulnerability is addressed by synchronizing path decoding behavior in Echo versions 4.15.3 and 5.2.0.
Potential Impact
An attacker can exploit this vulnerability to read static files on the server without proper authorization, potentially exposing sensitive information. The vulnerability does not affect integrity or availability but impacts confidentiality. The CVSS score of 7.5 reflects a high severity with network attack vector, low attack complexity, no privileges required, and no user interaction needed.
Mitigation Recommendations
This vulnerability is fixed in labstack Echo versions 4.15.3 and 5.2.0. Users should upgrade to at least these versions to remediate the issue. No other official remediation or temporary fixes are indicated. Patch status is confirmed by the vendor advisory stating the fix is included in these versions.
CVE-2026-55677: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in labstack echo
Description
Echo is a Go web framework. Prior to 4.15.3 and 5.2.0, Echo's router and static file handler disagree on URL path decoding. The router matches routes using the raw encoded path (preserving %2F as-is), while StaticDirectoryHandler unescapes %2F to / before resolving filesystem paths. This allows an attacker to bypass route-level access controls and read static files without authorization. This vulnerability is fixed in 4.15.3 and 5.2.0.
CVSS v3.1
Score 7.5high
Affected software
pkg:golang/github.com/labstack/echoRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In labstack Echo versions before 4.15.3 and 5.2.0, the router matches routes using the raw encoded URL path, preserving encoded slashes (%2F), while the StaticDirectoryHandler unescapes %2F to a slash before resolving filesystem paths. This discrepancy enables an attacker to bypass route-level access controls and access static files without authorization, constituting a path traversal vulnerability (CWE-22). The vulnerability is addressed by synchronizing path decoding behavior in Echo versions 4.15.3 and 5.2.0.
Potential Impact
An attacker can exploit this vulnerability to read static files on the server without proper authorization, potentially exposing sensitive information. The vulnerability does not affect integrity or availability but impacts confidentiality. The CVSS score of 7.5 reflects a high severity with network attack vector, low attack complexity, no privileges required, and no user interaction needed.
Mitigation Recommendations
This vulnerability is fixed in labstack Echo versions 4.15.3 and 5.2.0. Users should upgrade to at least these versions to remediate the issue. No other official remediation or temporary fixes are indicated. Patch status is confirmed by the vendor advisory stating the fix is included in these versions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-17T00:05:03.778Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3eae476e08203f7dc7e0cb
Added to database: 06/26/2026, 16:52:23 UTC
Last enriched: 06/26/2026, 17:06:56 UTC
Last updated: 06/27/2026, 05:50:05 UTC
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.