Skip to content
OpenAdvisories
Unscored GHSA-53rm-773f-4q8c RUSTSEC-2026-0523

MAX_STREAM_DATA frame can open streams beyond the stream limit

Published Sep 30, 2026 · Updated Nov 13, 2026 · Assigned by RUSTSEC

Description

When a MAX_STREAM_DATA frame named a peer-initiated bidirectional stream that was not open yet, `received_max_stream_data` treated the stream, and every lower-numbered stream, as opened without checking the stream ID against the limit advertised to the peer. RFC 9000 section 4.6 requires closing the connection with `STREAM_LIMIT_ERROR` in this case, and the STREAM and RESET_STREAM handlers already did so.

After the handshake, a peer can send one small MAX_STREAM_DATA frame naming a very large stream index, and `accept` then yields every stream up to that index. In `quinn`, a loop that keeps calling `accept_bi` can be handed more than 2^40 streams. Depending on the runtime, the endpoint runs out of memory, stops accepting new connections, or keeps busy indefinitely, even after the peer has gone away. Clients and servers that accept peer-initiated bidirectional streams are affected. Unidirectional streams are not.

The fix validates the stream ID in `received_max_stream_data` and adds a defensive check where streams are opened implicitly. It is in 0.11.19.

Affected packages

EcosystemPackageAffectedFixedRecord
crates.io quinn-proto >= 0.11.0, < 0.11.19 0.11.19 RUSTSEC-2026-0523

References