Is github.com/labstack/echo 3.2 vulnerable?

Go · 7 releases from 3.2.0 to 3.2.6 · latest github.com/labstack/echo is 3.3.10+incompatible · checked 18 Nov 2026

Yes: 1 known advisory

Yes. github.com/labstack/echo 3.2.6, the last 3.2 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?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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.2.6

  • HighCVE-2026-55677GHSA-vfp3-v2gw-7wfq25 Aug 2026

    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.2.x release

Affected: 3.2.0 to 3.2.6. Latest github.com/labstack/echo: 3.3.10+incompatible.

VersionKnown advisories
github.com/labstack/echo 3.2.6CVE-2026-55677
github.com/labstack/echo 3.2.5CVE-2026-55677
github.com/labstack/echo 3.2.4CVE-2026-55677
github.com/labstack/echo 3.2.3CVE-2026-55677
github.com/labstack/echo 3.2.2CVE-2026-55677
github.com/labstack/echo 3.2.1CVE-2026-55677
github.com/labstack/echo 3.2.0CVE-2026-55677

Which of your client projects are still on github.com/labstack/echo 3.2?

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.