Repository navigation
chore(deps): bump h2 to 0.4.16 (RUSTSEC-2026-0258) - #674
Merged
Merged
Conversation
RUSTSEC-2026-0258 ("h2 unbounded empty DATA frames", published 2026-08-17)
turned the repo-root `cargo audit` step red on every branch. Surgical
`cargo update -p h2 --precise 0.4.16` in the root Cargo.lock; nothing else
moves. dsm_storage_node (the h2 consumer) still checks clean.
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.
RUSTSEC-2026-0258 (
h2unbounded empty DATA frames, published 2026-08-17) turned the repo-rootcargo auditstep red on every branch (first seen on #673). Surgicalcargo update -p h2 --precise 0.4.16in the rootCargo.lock; nothing else moves.dsm_storage_node(theh2consumer) checks clean; rootcargo auditexits 0 (remaining entries are the pre-existing allowlisted warnings). Lockfile-only.