Is github.com/labstack/echo/v4 4.0 vulnerable?
Go · 1 release from 4.0.0 to 4.0.0 · latest github.com/labstack/echo/v4 is 4.16.5 · checked 18 Nov 2026
Yes: 32 known advisories
Yes. github.com/labstack/echo/v4 4.0.0, the last 4.0 release, is affected by 32 known security advisories (2 critical, 4 high, 10 medium, 16 low), including CVE-2026-118264, CVE-2022-40083, CVE-2026-118650. At least one has no fixed release yet.
Is your project on an affected github.com/labstack/echo/v4?
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/v4 4.0.0
Rate Limiter Bypass via Spoofed X-Forwarded-For Header in Default Configuration in github.com/labstack/echo
- Affected
- >=4.0.0
- Fixed in
- No fix released
URL-encoded path bypasses route/group middleware guarding a statically-served path in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Reverse Proxy Forwards Attacker-Supplied X-Real-IP to Upstream by Default in github.com/labstack/echo
- Affected
- >=4.0.0
- Fixed in
- No fix released
Cross-Site Scripting (XSS) via unsanitized JSONP callback in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has CSRF Protection Bypass via MethodOverride Rewriting POST to Safe Method in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Arbitrary Scheme Injection in WWWRedirect/NonWWWRedirect Middlewares via X-Forwarded-Proto in github.com/labstack/echo
- Affected
- <4.15.2
- Fixed in
- 4.15.2
Echo: HTTPS Redirect and HSTS Bypass via Unconditional Trust of Forwarded Scheme Headers in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo static file middleware route protection bypass via encoded dot-dot traversal in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has Open Redirect via Control-Character Prefix Defeating sanitizeURI in github.com/labstack/echo
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has a Static Middleware Double-Unescape Path Traversal in github.com/labstack/echo
- Affected
- <4.15.3
- Fixed in
- 4.15.3
Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls in github.com/labstack/echo
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Echo: BodyDump captures request and response bodies without size limits in v4 in github.com/labstack/echo
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Echo: Decompress permits unbounded gzip expansion in v4 in github.com/labstack/echo
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Echo: HTTPS Redirect and HSTS Bypass via Unconditional Trust of Forwarded Scheme Headers
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo static file middleware route protection bypass via encoded dot-dot traversal
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has a Static Middleware Double-Unescape Path Traversal
- Affected
- <4.15.3
- Fixed in
- 4.15.3
Echo has Open Redirect via Control-Character Prefix Defeating sanitizeURI
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has Arbitrary Scheme Injection in WWWRedirect/NonWWWRedirect Middlewares via X-Forwarded-Proto
- Affected
- <4.15.2
- Fixed in
- 4.15.2
Echo's middleware.Static: `%2F`-encoded path bypasses route/group middleware guarding a statically-served path
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo vulnerable to Reflected Cross-Site Scripting (XSS) via unsanitized JSONP callback in Context.JSONP / Context.JSONPBlob
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo has Rate Limiter Bypass via Spoofed X-Forwarded-For Header in Default Configuration
- Affected
- >=4.0.0 <=4.16.2
- Fixed in
- No fix released
Echo has CSRF Protection Bypass via MethodOverride Rewriting POST to Safe Method
- Affected
- <4.16.0
- Fixed in
- 4.16.0
Echo: Reverse Proxy Forwards Attacker-Supplied X-Real-IP to Upstream by Default
- Affected
- >=4.0.0 <=4.16.2
- Fixed in
- No fix released
Echo: Decompress permits unbounded gzip expansion in v4
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Echo: Rejected WebSocket upgrades can bypass Echo route-level access controls
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Echo: BodyDump captures request and response bodies without size limits in v4
- Affected
- >=4.0.0 <4.16.1
- Fixed in
- 4.16.1
Encoded slash (%2F) bypasses route-level protection and exposes static files in github.com/labstack/echo/v4 and github.com/labstack/echo/v5
- Affected
- <4.15.3
- Fixed in
- 4.15.3
Echo: Encoded slash (%2F) bypasses route-level protection and exposes static files
- Affected
- <4.15.3
- Fixed in
- 4.15.3
Echo vulnerable to directory traversal
- Affected
- <4.2.0
- Fixed in
- 4.2.0
Open redirect in github.com/labstack/echo/v4
- Affected
- <4.9.0
- Fixed in
- 4.9.0
Labstack Echo Open Redirect vulnerability
- Affected
- <4.9.0
- Fixed in
- 4.9.0
Directory traversal on Windows in github.com/labstack/echo/v4
- Affected
- <4.1.18-0.20201215153152-4422e3b66b9f
- Fixed in
- 4.1.18-0.20201215153152-4422e3b66b9f
Which of your client projects are still on github.com/labstack/echo/v4 4.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/labstack/echo/v4 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/labstack/echo/v4 versions
- github.com/labstack/echo/v4 4.3
- github.com/labstack/echo/v4 4.2
- github.com/labstack/echo/v4 4.1
- github.com/labstack/echo/v4 4.16
- github.com/labstack/echo/v4 4.15
- github.com/labstack/echo/v4 4.14
- github.com/labstack/echo/v4 4.13
- github.com/labstack/echo/v4 4.12
- github.com/labstack/echo/v4 4.11
- All github.com/labstack/echo/v4 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.