fix(deps): bump quinn-proto to 0.11.15 (RUSTSEC-2026-0185)#141
Merged
jacderida merged 1 commit intoJul 7, 2026
Merged
Conversation
quinn-proto <0.11.15 is vulnerable to remote memory exhaustion via unbounded out-of-order stream reassembly (RUSTSEC-2026-0185). It reaches this workspace transitively through saorsa-transport -> quinn -> quinn-proto over a caret range, so the patched 0.11.15 resolves in the committed lockfile with no Cargo.toml constraint change. Keeps `cargo audit` green and any distributed binaries off the vulnerable version. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bump
quinn-proto0.11.14 → 0.11.15in the committed lockfile to clear RUSTSEC-2026-0185 (remote memory exhaustion via unbounded out-of-order stream reassembly).Details
saorsa-transport → quinn → quinn-proto, all over caret ranges — so 0.11.15 resolves with noCargo.tomlchange, lockfile-only.< 0.11.15, patched>= 0.11.15.cargo auditgreen and keeps any binaries built from this repo off the vulnerable version.Lockfile-only; no code or API impact.