fix: update rand and rustls-webpki to resolve 4 security advisories#736
Merged
Conversation
The nightly security audit reported the following advisories against transitive dependencies pinned in Cargo.lock: - RUSTSEC-2026-0098 (rustls-webpki 0.103.10): URI name constraints were ignored and therefore accepted. Not reachable from this crate (no URI name assertions), but bumping to 0.103.13 brings in the fix. - RUSTSEC-2026-0099 (rustls-webpki 0.103.10): DNS wildcard names were accepted under permitted-subtree name constraints. Reachable only after misissuance. - RUSTSEC-2026-0104 (rustls-webpki 0.103.10): reachable panic when parsing a CRL with an empty BIT STRING in onlySomeReasons. Not reachable unless the application parses CRLs. - RUSTSEC-2026-0097 (rand 0.8.5, informational/unsound): unsound when a custom log logger calls rand::rng() reentrantly during reseeding. Not reachable from this crate's usage of rand via tokio-retry. All four are transitive: rustls-webpki comes in via hyper-rustls (dev-dep) and rand via tokio-retry. Both bumps are within the same SemVer minor (0.103.10 -> 0.103.13, 0.8.5 -> 0.8.6) so no API churn. Lockfile-only change. cargo build --tests and cargo test --lib pass.
vicheey
approved these changes
May 27, 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 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.
Summary
The nightly Security audit workflow reported 4 advisories against transitive dependencies pinned in
Cargo.lock. This PR is a lockfile-only bump that picks up the patches.rustls-webpki0.103.10→0.103.13rustls-webpki0.103.10→0.103.13rustls-webpki0.103.10→0.103.13rand(unsound)0.8.5→0.8.6loglogger callingrand::rng()reentrantly during reseeding.Both bumps are within the same SemVer minor, so no API churn for this crate.
rustls-webpkiis pulled in viahyper-rustls(dev-dep).randis pulled in viatokio-retry.Out of scope
The audit workflow itself emitted
Resource not accessible by integrationbecause it's missingissues: writepermission. That's already being addressed in #718, so it's not part of this PR.Test plan
cargo build --testscleancargo test --lib— all 21 tests passSecurity auditrun is green