Repository navigation
fix(deps): bump rustls-webpki and webpki roots for security advisories - #159
Merged
Merged
Conversation
Update rustls-webpki to 0.103.16 (RUSTSEC-2026-0382) and webpki-roots and webpki-root-certs to 1.0.11 (RUSTSEC-2026-0381, RUSTSEC-2026-0383).
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
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
Clear three RustSec advisories that make the
auditcheck fail on every PR, including Dependabot #156, #157, and #158:rustls-webpki0.103.15. Certificate verification may accept distrusted intermediates. Fixed in 0.103.16.webpki-roots1.0.9. Bundled roots allow trust in distrusted emSign intermediates. Fixed in 1.0.10.webpki-root-certs1.0.9. Same emSign issue. Fixed in 1.0.10.All three are transitive dependencies:
rustls-webpkicomes in throughrustls/rustls-platform-verifierviareqwest.webpki-root-certscomes in throughrustls-platform-verifier.webpki-rootscomes in throughureq.cargo update -pmoves them to 0.103.16, 1.0.11, and 1.0.11. This changes only the lockfile, with no source changes and no new audit ignores.Verification
cargo audit: no vulnerabilitiescargo test: passcargo clippy --all-targets --all-features -- -D warnings: cleancargo fmt --check: cleancargo build --release: pass