Vulnerability · RUSTSEC-2026-0341
Stream reassembly memory-exhaustion guard in quinn-proto can be bypassed
Published Aug 17, 2026 · RustSec Rust
Open the advisory
Exploitation likelihood is not on this record for RUSTSEC-2026-0341. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.
Gaps on this record
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Not established
- Affected products
- RustSec Rust
The fix for RUSTSEC-2026-0185 in 0.11.15 added a cap on the number of chunks buffered by the that reassembles out-of-order stream data. However, the cap was only checked inside the branch that triggers defragmentation, which only runs when the estimated over-allocation exceeds a threshold proportional to the amount of buffered data. Frames handled entirely by the unordered-read deduplication loop returned before the check ran at all. A peer sending one small gapped STREAM frame per packet (for example, 6-byte frames separated by 1-byte gaps) keeps the per-chunk overhead below the defragmentati
No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.
How to fix RUSTSEC-2026-0341
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for RUSTSEC-2026-0341. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Aug 17, 2026 · RustSec Advisory DB
Detected
The fix for RUSTSEC-2026-0185 in 0.11.15 added a cap on the number of chunks buffered by the that reassembles out-of-order stream data. However, the cap was only checked inside the branch that triggers defragmentation, which only runs when the estimated over-allocation exceeds a threshold proportional to the amount of buffered data. Frames handled entirely by the unordered-read deduplication loop
Sources
- RustSec Advisory DBVendor advisoryRUSTSEC-2026-0341
The fix for RUSTSEC-2026-0185 in 0.11.15 added a cap on the number of chunks buffered by the that reassembles out-of-order stream data. However, the cap was only checked inside the branch that triggers defragmentation, which only runs when the estimated over-allocation exceeds a
crates.io
Freshness
Last verified in this catalog Unknown date. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.