Is github.com/labstack/echo 1.1 vulnerable?
Go · 1 release from 1.1.0 to 1.1.0 · latest github.com/labstack/echo is 3.3.10+incompatible · checked 18 Nov 2026
Yes: 1 known advisory
Yes. github.com/labstack/echo 1.1.0, the last 1.1 release, is affected by 1 known security advisory (1 high), including CVE-2026-55677. At least one has no fixed release yet.
Is your project on an affected github.com/labstack/echo?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/labstack/echo 1.1.0
Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files
- Affected
- <=3.3.10
- Fixed in
- No fix released
Which of your client projects are still on github.com/labstack/echo 1.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/labstack/echo version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/labstack/echo versions
- github.com/labstack/echo 2.0
- github.com/labstack/echo 1.4
- github.com/labstack/echo 1.2
- github.com/labstack/echo 1.0
- github.com/labstack/echo 0.0
- github.com/labstack/echo 3.3
- github.com/labstack/echo 3.2
- github.com/labstack/echo 3.1
- github.com/labstack/echo 3.0
- github.com/labstack/echo 2.2
- All github.com/labstack/echo advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.