fix(deps): update rustls to 0.23.45 for RUSTSEC-2026-0285 - #1069
Merged
Merged
Conversation
Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Summary
cargo deny checknow fails on every pull request because RUSTSEC-2026-0285 (rustls accepted TLS 1.3 handshake messages across encryption level boundaries) was published against the lockedrustls0.23.43. The fixed release is 0.23.45. Dependabot's grouped update (#1056) only reaches 0.23.44, so it does not clear the advisory.This changes only the
rustlsentry inCargo.lock(cargo update -p rustls --precise 0.23.45). No manifest or other dependency moves.Owning area: workspace dependencies.
Checks
cargo deny check: advisories, bans, licenses and sources ok. The same command on currentmainreports RUSTSEC-2026-0285.cargo check --locked -p registry-bregNotes
Security-sensitive: TLS dependency. The advisory notes the handshake transcript stays authenticated, so the practical effect was accepting plaintext handshake messages that should have been encrypted.
DCO
Signed-off-bytrailer.