chore(deps): ignore RUSTSEC-2026-0049 (rustls-webpki) until rustls can be upgraded#24986
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
pront
changed the title
pront
added
the
no-changelog
pront
changed the title
thomasqueirozb
approved these changes
Mar 23, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
make check-denyfails due to RUSTSEC-2026-0049 (rustls-webpki 0.101.7): a vulnerability where certificates with multiple CRL distribution points only have the first one checked, so subsequent CRLs can be silently skipped for revocation. The fix requiresrustls-webpki >= 0.103.10, which means upgradingrustlsfrom0.21to0.23+— a significant chain that touchesaws-smithy-http-client,hyper-rustls,tokio-rustls, andtokio-tungstenite.Some crates have not yet updated to
rustls-webpki >= 0.103.10, such as async-nats. Others are permanently stuck on older versions of rustls since we're using very outdated versions, like tonic/reqwest/bollard/etc. These depend on the http 1.0 upgradeVector configuration
N/A
How did you test this PR?
Output:
advisories ok, bans ok, licenses ok, sources okChange Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
httpcrate to version 1.0.0 #19179