undici WebSocket client vulnerable to denial of service via fragment count bypass
Historical advisory saved 4 Nov 2026 03:57:35 UTC. The publisher may have updated it since then. Latest advisory.
osv · GHSA-vxpw-j846-p89q
Published## Impact The undici WebSocket client enforces `maxPayloadSize` on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that each pass per-frame and cumulative-size validation, collectively causing unbounded memory growth in the client process. The result is memory exhaustion and a denial of service. Affected applications are those using the undici WebSocket client (`new WebSocket(...)`) or the `WebSocketStream` API that can be induced to connect to an attacker-controlled or compromised WebSocket endpoint. All releases starting at undici 6.17.0 are affected. ## Patches Upgrade to undici v6.27.0, v7.28.0 or v8.5.0. ## Workarounds No workaround is available. The fix must be applied through an upgrade.
- Source published
- 19 Jun 2026 14:22:01 UTC
- Source modified
- 4 Nov 2026 03:45:10 UTC
- Saved here
- 4 Nov 2026 03:57:35 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Publisher rating · HIGH