Is github.com/labstack/echo 3.3 vulnerable?
Go · 11 releases from 3.3.0 to 3.3.10 · latest github.com/labstack/echo is 3.3.10+incompatible · checked 18 Nov 2026
Yes: 1 known advisory
Yes. github.com/labstack/echo 3.3.10, the last 3.3 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 3.3.10
Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files
- Affected
- <=3.3.10
- Fixed in
- No fix released
Every github.com/labstack/echo 3.3.x release
Affected: 3.3.0 to 3.3.10. Latest github.com/labstack/echo: 3.3.10+incompatible.
| Version | Known advisories |
|---|---|
| github.com/labstack/echo 3.3.10 | CVE-2026-55677 |
| github.com/labstack/echo 3.3.9 | CVE-2026-55677 |
| github.com/labstack/echo 3.3.8 | CVE-2026-55677 |
| github.com/labstack/echo 3.3.7 | CVE-2026-55677 |
| github.com/labstack/echo 3.3.6 | CVE-2026-55677 |
| github.com/labstack/echo 3.3.5 | CVE-2026-55677 |
| github.com/labstack/echo 3.3.4 | CVE-2026-55677 |
| github.com/labstack/echo 3.3.3 | CVE-2026-55677 |
| github.com/labstack/echo 3.3.2 | CVE-2026-55677 |
| github.com/labstack/echo 3.3.1 | CVE-2026-55677 |
| github.com/labstack/echo 3.3.0 | CVE-2026-55677 |
Which of your client projects are still on github.com/labstack/echo 3.3?
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
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.