Advisory

GHSA-9969-6676-49h5

Also known as: CVE-2026-118262, GO-2026-6838

Summary

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

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-10-23 20:50 UTC
Modified
2026-11-05 23:25 UTC

Affected packages and fixes

github.com/labstack/echo/v4

Go · All systems

Affected

  • introduced 4.15.0, fixed 4.16.1 (semver)

Fixed versions

4.16.1

Fix

github.com/labstack/echo/v5

Go · All systems

Affected

  • introduced 5.0.0, fixed 5.4.1 (semver)

Fixed versions

5.4.1

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences