Is github.com/labstack/echo/v4 4.16 vulnerable?
Go · 6 releases from 4.16.0 to 4.16.5 · latest github.com/labstack/echo/v4 is 4.16.5 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. github.com/labstack/echo/v4 4.16.5, the last 4.16 release, is affected by 2 known security advisories (2 low), including CVE-2026-118653, CVE-2026-118651. 10 more affect earlier 4.16.x releases. 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.16.5
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
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
Fixed within 4.16.x, affecting earlier releases
Echo: WebSocket proxy can retain connections and handlers after client disconnect in github.com/labstack/echo
- Affected
- >=4.15.0 <4.16.1
- Fixed in
- 4.16.1
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 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: 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: WebSocket proxy can retain connections and handlers after client disconnect
- Affected
- >=4.15.0 <4.16.1
- Fixed in
- 4.16.1
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
Every github.com/labstack/echo/v4 4.16.x release
Affected: 4.16.0 to 4.16.5.
| Version | Known advisories |
|---|---|
| github.com/labstack/echo/v4 4.16.5 | CVE-2026-118653, CVE-2026-118651 |
| github.com/labstack/echo/v4 4.16.4 | CVE-2026-118653, CVE-2026-118651 |
| github.com/labstack/echo/v4 4.16.3 | CVE-2026-118653, CVE-2026-118651 |
| github.com/labstack/echo/v4 4.16.2 | CVE-2026-118653, CVE-2026-118651, CVE-2026-118653, CVE-2026-118651 |
| github.com/labstack/echo/v4 4.16.1 | CVE-2026-118653, CVE-2026-118651, CVE-2026-118653, CVE-2026-118651 |
| github.com/labstack/echo/v4 4.16.0 | CVE-2026-118653, CVE-2026-118651, CVE-2026-118262, CVE-2026-118264, CVE-2026-118260, CVE-2026-118261, CVE-2026-118653, CVE-2026-118651, CVE-2026-118262, CVE-2026-118261, CVE-2026-118264, CVE-2026-118260 |
Which of your client projects are still on github.com/labstack/echo/v4 4.16?
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
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.