Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 14 September 2026.
- Which products and versions are affected?
- quinn-proto (crates.io) SEMVER:introduced=0.7.0,fixed=0.11.18; Quinn-Rs Quinn-Proto 0.7.0 to 0.11.17.
- Is there a fix for This vulnerability?
- Yes. quinn-proto (crates.io): upgrade to 0.11.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run quinn-proto (crates.io) or Quinn-Rs Quinn-Proto at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- quinn-proto (crates.io): upgrade to 0.11.18 or later
cargo update -p quinn-proto
Technical details
When a stream is read in unordered mode via RecvStream::read(false), quinn-proto deduplicates received data by storing ranges in a RangeSet through its replace method. Processing an incoming STREAM frame with an empty payload causes the Drop implementation of the iterator to insert an empty range, violating the invariant that stored ranges must be non-empty. Subsequent overlapping frames trigger a panic during stream processing. A remote peer can exploit this with five small STREAM frames (including two zero-length frames) once unordered read mode is active.
Affected products
- quinn-rs quinn-proto 0.7.0 to 0.11.17
Identifiers
- GHSA-465w-v9q3-7j98
- RUSTSEC-2026-0338
Timeline
- 2026-09-14: disclosed
- 2026-10-12: advisory