Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
RUSTSEC-2026-0342
quinn-proto bounds its queue of received datagrams by charging each queued frame's payload length
against TransportConfig::datagram_receive_buffer_size, evicting the oldest datagrams when the
limit is exceeded. A DATAGRAM frame with an empty payload was charged zero bytes, so it never
triggered eviction and was appended to the queue, which has no other bound.
DATAGRAM frames are not subject to flow control. A peer that has completed the handshake can
therefore send a stream of empty DATAGRAM frames and grow the receiver's heap without limit until
the process is killed. An application that reads incoming datagrams but does so more slowly than
the peer sends them is still affected. Receiving datagrams is enabled by default, so all endpoints
that do not explicitly set datagram_receive_buffer_size(None) are affected.
The send path had the same accounting flaw: an application could enqueue an unbounded number of
empty outgoing datagrams without ever receiving SendDatagramError::Blocked.
The flaw was corrected in 0.11.17 by accounting for the fixed per-datagram overhead in both directions, so that every queued datagram consumes buffer space.
Thanks to @alexpyattaev for reporting this issue.
Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.
Drag and drop some file here, or click to select
Measures severity based on intrinsic characteristics of the vulnerability, independent of environment.
No exploitation activity has been observed at this time. Continue routine monitoring.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard