HighGHSA-9969-6676-49h5CVE-2026-118262GO-2026-6838

Echo: WebSocket proxy can retain connections and handlers after client disconnect

Published 23 Oct 2026 · Updated 5 Nov 2026

Is your project on an affected github.com/labstack/echo/v4?

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

Affected packages

Affected
>=4.15.0 <4.16.1
Fixed in
4.16.1
Update to the fixed version for your release line, for example:go get github.com/labstack/echo/v4@v4.16.1
Affected
>=5.0.0 <5.4.1
Fixed in
5.4.1
Update to the fixed version for your release line, for example:go get github.com/labstack/echo/v5@v5.4.1

Details

Impact

Echo's Proxy middleware could retain a handler, copy goroutines and network connections after a WebSocket client disconnected if the upstream kept its connection open. The raw proxy waited for both copy directions to finish without reliably closing the other connection when one direction ended. Rejected upgrade responses with HTTP keep-alive were one way to trigger this behavior.

Repeated connections can accumulate resources and cause denial of service. The impact depends on the proxy route's accessibility, upstream behavior and configured connection deadlines. This is a medium-severity resource-retention issue; no confidentiality or integrity impact is claimed.

Affected versions and patch

Affected versions are v4.15.0 through v4.16.0 and v5.0.0 through v5.4.0. The regression was introduced by commit e2133320c7, merged in #2852.

Upgrade to v4.16.1 or v5.4.1. The patch uses Go's HTTP reverse proxy, preserves ordinary HTTP handling for rejected upgrades, and closes both sides of a WebSocket tunnel when either direction ends. It also covers an upstream that receives client EOF but deliberately keeps its side open.

Fix commits: v4, v5.

Workarounds

Disable WebSocket proxy routes until upgrading, or apply bounded connection lifetimes and resource limits at the frontend and upstream. Server idle timeouts alone may not cover hijacked WebSocket connections.

Credits

Reported by @irisitymichaelgrundberg.

Is GHSA-9969-6676-49h5 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/labstack/echo/v4, and gives you the command that fixes it.

More advisories for github.com/labstack/echo/v4

  • LowCVE-2026-118653Rate Limiter Bypass via Spoofed X-Forwarded-For Header in Default Configuration in github.com/labstack/echo · 5 Nov 2026
  • LowCVE-2026-118650URL-encoded path bypasses route/group middleware guarding a statically-served path in github.com/labstack/echo · 5 Nov 2026
  • LowCVE-2026-118651Reverse Proxy Forwards Attacker-Supplied X-Real-IP to Upstream by Default in github.com/labstack/echo · 5 Nov 2026
  • LowCVE-2026-118652Cross-Site Scripting (XSS) via unsanitized JSONP callback in github.com/labstack/echo · 5 Nov 2026
  • LowCVE-2026-118266Echo has CSRF Protection Bypass via MethodOverride Rewriting POST to Safe Method in github.com/labstack/echo · 5 Nov 2026
  • LowCVE-2026-118658Arbitrary Scheme Injection in WWWRedirect/NonWWWRedirect Middlewares via X-Forwarded-Proto in github.com/labstack/echo · 5 Nov 2026
All 33 advisories for github.com/labstack/echo/v4

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.