Ignore RUSTSEC-2026-0258 in cargo audit - #972
Open
nbarbier-265 wants to merge 1 commit into
Open
Conversation
h2 0.3.27 comes in through the same legacy aws chain as the existing rustls-webpki ignores: dial9-tokio-telemetry -> aws-sdk-s3-transfer-manager -> aws-config -> aws-smithy-http-client, which still uses hyper 0.14. The advisory's only fix is h2 >= 0.4.16 and no 0.3.x patch exists, so this cannot be resolved from this workspace's manifests. The vulnerable code needs a malicious HTTP/2 peer; in this chain h2 is only a TLS client to AWS endpoints. Every CI run has failed the cargo audit step since the advisory was published on 2026-08-17.
nbarbier-265
force-pushed
the
audit-ignore-h2-0258
branch
from
August 20, 2026 21:25
39a15c4 to
c2cd34a
Compare
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
2 participants
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.
Every CI run fails the
cargo auditstep since 2026-08-17, when RUSTSEC-2026-0258 (h2 0.3: unbounded empty DATA frames) was published. All PRs currently show a red X regardless of their contents.h2 0.3.27 enters the lockfile through the same legacy aws chain as the existing rustls-webpki ignores:
dial9-tokio-telemetry->aws-sdk-s3-transfer-manager->aws-config->aws-smithy-http-client, which still uses hyper 0.14. The advisory's only fix is h2 >= 0.4.16 and no 0.3.x patch exists, so this can't be resolved from this workspace's manifests — same situation as the three rustls-webpki ignores already in.cargo/audit.toml, and the same removal condition applies (the upstream aws-s3-transfer-manager-rs migration off the legacy chain).Exploitability in this position is limited: the advisory needs a malicious HTTP/2 peer, and in this chain h2 0.3 only acts as a TLS client to AWS endpoints.
Verified locally with CI's exact steps:
cargo generate-lockfile --ignore-rust-version && cargo auditfails before this change and exits 0 after, with the same 4 allowed warnings as before.