WebSocket compression-bomb memory use fixed
medium2026-02-23 Security advisory GHSA-qrvq-68c2-7grw published after the release
Previously, decompressing a highly compressed frame could create a very large buffer before the server rejected it for exceeding the maximum payload size, risking excessive memory use and server termination. Decompression now stops at the configured maximum payload size, or the default maximum if none is specified, and returns ErrMaxPayload.
Show release-note lines
- WebSocket connections will now correctly limit the buffer size during decompression (#7625, thanks to Pavel Kokout at Aisle Research)github.com/nats-io/nats-server/releases/tag/v2.12.3
This was fixed in the v2.11 series with v2.11.12 and in the v2.12 series with v2.12.3.github.com/nats-io/nats-server/security/advisories/GHSA-qrvq-68c2-7grw