fix(deps): bump h2 to 0.4.16 to resolve RUSTSEC-2026-0258 - #1619
Open
ygd58 wants to merge 1 commit into
Open
Conversation
h2 <0.4.16 accepts and queues unbounded empty DATA frames without limit, which can lead to unbounded memory usage or a panic (DoS) if streams are not actively drained. h2 is pulled in via tonic/reqwest (client-side HTTP/2 usage for remote RPC/geyser connections). Patch-level bump only, dependency spec is identical between 0.4.15 and 0.4.16 (verified against the crates.io index) so no API surface changed. Verified: cargo build --release succeeds cleanly for the full workspace. Full test suite could not be run in this environment due to a pre-existing, unrelated cargo build-sbf/edition2024 toolchain mismatch (reproduced identically on unpatched Cargo.lock via git stash, confirming it is unrelated to this change). Advisory: GHSA-q83h-524g-xf6h
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
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
1 participant
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.
What changed
Bump
h2from 0.4.15 to 0.4.16 in Cargo.lock.Why
h2 <0.4.16 accepts and queues unbounded empty DATA frames without limit, which can lead to unbounded memory usage or a panic (DoS) if streams are not actively drained (GHSA-q83h-524g-xf6h). h2 is pulled in via tonic/reqwest for client-side HTTP/2 usage (remote RPC/geyser connections).
Compatibility
None — patch-level bump only. Dependency spec is identical between 0.4.15 and 0.4.16 per the crates.io index, so no API surface changed.
Validation
cargo build --releasesucceeds cleanly for the full workspacecargo build-sbf/edition2024 toolchain mismatch in this environment (reproduced identically on unpatched Cargo.lock via git stash, confirming it's unrelated to this change)Advisory: GHSA-q83h-524g-xf6h