Repository navigation
fix: update rustls to 0.23.46 for its security advisories - #66
Merged
animeshchaudhri merged 1 commit intoOct 21, 2026
Merged
Conversation
rustls 0.23.43, the TLS stack behind every HTTPS request, is affected
by RUSTSEC-2026-0349, -0285, -0346 and -0348. Two apply to an HTTP
client: a ServerHello that can downgrade later connections to
classical key exchange (0349), and TLS 1.3 handshake messages
accepted across encryption levels (0285). 0348 needs the brotli
feature, which is off, and 0346 concerns Debug output of session
values. 0.23.46 fixes all four and is semver-compatible; it also
moves aws-lc-rs to 1.18.2, aws-lc-sys to 0.46.0 and rustls-webpki
to 0.103.15.
crossbeam-epoch goes from 0.9.18 to 0.9.21 for RUSTSEC-2026-0204, an
invalid pointer dereference in its fmt::Pointer impl.
cargo update -p rustls
cargo update -p crossbeam-epoch
Lock-only.
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.
cargo auditreports four advisories against rustls 0.23.43, the TLS stack behind every HTTPS request rustman sends:Debugimpls for client session values expose TLS secrets.The first two apply to an HTTP client like this one; 0348 needs rustls's
brotlifeature, which is off here. 0.23.46 fixes all four and is semver-compatible. The update also movesaws-lc-rsfrom 1.17.0 to 1.18.2,aws-lc-sysfrom 0.41.0 to 0.46.0 (AWS-LC 5.11.0) andrustls-webpkifrom 0.103.13 to 0.103.15.crossbeam-epochgoes from 0.9.18 to 0.9.21 for RUSTSEC-2026-0204, an invalid pointer dereference in itsfmt::Pointerimpl.It only touches
Cargo.lock, and it is independent of #65: squash-merged in either order, the two give the same tree, and cargo accepts the combined lock unchanged under--locked.cargo auditgoes from 15 vulnerabilities to 10. The rest arequinn-proto, which is in the lock but not compiled on Linux;quick-xml, which onlywayland-scanneruses at build time; andzip8, whose fix is zip 9 and needs calamine to move first. Neither calamine nor the updater calls theextractAPIs those three advisories are about.Testing
cargo test: 139 passed and 3 ignored with default features, 131 and 3 with--no-default-features, the same as master.cargo check --all-targets --target x86_64-pc-windows-gnupasses with master's one warning (APP_IDis never used).rust-versionfloors are the same as on master.dpkg-buildpackage, whoseCFLAGScarry-O2, aws-lc-sys 0.46.0 compiles without the jitterentropy error that 0.45.0 hit ("The CPU Jitter random number generator must not be compiled with optimizations." in 1.18.1 and -sys 0.45.0 aws/aws-lc-rs#1252)..text. I have not traced which upstream change accounts for it.Not tested on macOS, nor at runtime on Windows; WebSocket over TLS was not exercised.