chore(deps): bump vulnerable rust packages#10156
Merged
Merged
Conversation
Address open cargo dependabot alerts by bumping the affected crates in
Cargo.lock and the Bazel-managed Cargo.Bazel.{toml,json}.lock files.
Bumped:
- openssl 0.10.76 -> 0.10.79
- rand (0.9.x and 0.10.x bumped to latest patched)
- actix-http 3.12.0/3.9.0 -> 3.12.1 (main) / 3.12.0 (bazel)
- tar 0.4.44 -> 0.4.45
- rustls-webpki (0.103.x bumped to 0.103.13)
- lz4_flex 0.11.5 -> 0.11.6 (bazel)
- quinn-proto 0.11.7 -> 0.11.14 (bazel)
Bazel lock regenerated via `CARGO_BAZEL_REPIN=<crate> bazel build @crate_index//...`.
Not addressed (require deeper dependency-chain bumps outside this PR):
- rand 0.8.5: ic-bn-lib v0.1.15 has `rand = "=0.8.5"` exact pin
- rustls-webpki 0.102.8 / 0.101.7: warp 0.3.7 -> tokio-rustls 0.25 -> rustls 0.22
- hickory-proto 0.25.2: requires bumping hickory-resolver to 0.26
- actix-http 3.12.1 in bazel lock: splicer settles at 3.12.0
Also no upstream fix available: wee_alloc (unmaintained), atty, rsa Marvin
attack (timing), paramiko SHA-1.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Pin actix-http directly via crate_universe in bazel/rust.MODULE.bazel so the splicer pulls in 3.12.1 (closes the remaining bazel-lock instance of the HTTP/1.1 CL.TE request-smuggling alert #474). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This reverts commit 278508c.
Keep quinn-proto at 0.11.7 in the bazel lock. The 0.11.7 -> 0.11.14 bump broke some tests, so leave dependabot alert #409 open until quinn / its transitive consumers can absorb the upgrade separately. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…s-dependabot # Conflicts: # Cargo.Bazel.json.lock
basvandijk
approved these changes
May 11, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to a conflict with the base branch
…s-dependabot # Conflicts: # Cargo.Bazel.json.lock
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
Resolves the addressable open cargo ecosystem dependabot alerts on this repo by bumping affected crates in
Cargo.lockand the Bazel-managed lock files. Sanity-checked by building//rs/canister_client:canister_clientlocally (~2.4k actions, all succeeded).Closed alerts
Not addressable in this PR
These either have no upstream fix, are pinned by a transitive constraint that would require updating a dependent crate beyond the scope of a security bump, or were tried and rejected because they broke tests:
quinn-proto 0.11.7→0.11.14rand 0.8.5ic-bn-lib v0.1.15hasrand = "=0.8.5"exact pin; tried bumping ic-bn-lib to 0.1.19 but it broke tests (alerts #476, #479, #481)rustls-webpki 0.101.7/0.102.8warp 0.3.7→tokio-rustls 0.25→rustls 0.22(alerts #469-472)hickory-proto 0.25.2hickory-resolverto 0.26.x (alerts #502-505)paramiko/wee_alloc/attyrsa <= 0.9.6Marvin attack timingrs/validator/fuzz/Cargo.lockalerts[workspace.package]) and the file is unused by Bazel; would need a separate manifest-repair PR (#294, #318, #380, #393, #461, #462, #463, #481, #317)rs/universal_canister/impl/Cargo.lockalertswee_alloc(unmaintained, no fix) andatty(no fix) — #460, #247How regenerated
Note on
bazel/rust.MODULE.bazel: added a directcrate.spec(package = "actix-http", version = "^3.12.1")to force the splicer past 3.12.0 — without it the resolver was free to keep the older transitive version.Test plan
//rs/canister_client:canister_clientsucceeds (done locally)🤖 Generated with Claude Code