Bump rustls to 0.23.45 for RUSTSEC-2026-0285 - #851
Merged
Merged
Conversation
cargo audit started failing CI: rustls 0.23.42 accepts TLS 1.3 handshake messages across encryption level boundaries. Fixed in 0.23.45, which also pulls rustls-webpki 0.103.15. Also bumps chacha20 and wnaf off yanked versions, clearing the two yanked warnings in the same audit run. Re-resolution dedups windows-sys 0.52.0 down to a single remaining dependent.
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.
cargo audit is failing CI on main: rustls 0.23.42 is hit by RUSTSEC-2026-0285 (TLS 1.3 handshake messages accepted across encryption level boundaries, medium). Fixed in 0.23.45, which also pulls rustls-webpki 0.103.15.
Lockfile only — rustls is already declared as
0.23in Cargo.toml, so no manifest change needed.Also bumps chacha20 0.10.1 -> 0.10.2 and wnaf 0.14.0 -> 0.14.1, both off yanked releases, which clears the two yanked warnings in the same audit run. Re-resolution deduped windows-sys 0.52.0 from six dependents down to one.
Verified locally:
cargo auditexits 0 (only the pre-existing, already-ignored fxhash unmaintained warning remains) andcargo check --locked --all-targetspasses. Also batch-queried OSV for all 636 locked crates — fxhash is the only hit, and it's already in .osv-scanner.toml, so the OSV step (which was skipped last run because audit failed first) should pass too.