Repository navigation
fix(deps): clear RUSTSEC-2026-0385 and RUSTSEC-2026-0387 - #665
Merged
Merged
Conversation
Destynova2
force-pushed
the
fix/deps-crypto-advisories
branch
from
October 28, 2026 14:34
52e92a6 to
a5c41f8
Compare
Destynova2
enabled auto-merge (squash)
October 28, 2026 14:34
cargo-deny and cargo-audit started failing on two freshly published advisories against transitive crypto crates (no grob code change pulled them in): - RUSTSEC-2026-0385 (ctutils): non-constant-time mask generation and u128 comparisons. Fixed by ctutils 0.4.2 -> 0.4.6. - RUSTSEC-2026-0387 (crypto-bigint): timing variability in operations intended to be constant-time. Fixed on the 0.7.x line by crypto-bigint 0.7.5 -> 0.7.10 (0.7.6, the first fixed release, is yanked). A second crypto-bigint 0.5.5 remains in the tree, pulled unconditionally by age 0.12.1 (the latest release) through its non-optional hpke/p256 0.13 -> elliptic-curve 0.13.8 dependencies. The advisory has no patched 0.5.x release and no grob feature toggles that path off, so RUSTSEC-2026-0387 is ignored, with a documented and dated entry, in both deny.toml and the in-sync .cargo/audit.toml. Remove both the moment age ships on a fixed crypto-bigint.
Destynova2
force-pushed
the
fix/deps-crypto-advisories
branch
from
October 28, 2026 15:36
a5c41f8 to
f9f1c37
Compare
Destynova2
added a commit
that referenced
this pull request
Oct 28, 2026
## 🤖 New release * `grob`: 0.36.128 -> 0.36.129 <details><summary><i><b>Changelog</b></i></summary><p> <blockquote> ## [0.36.129](v0.36.128...v0.36.129) - 2026-10-28 ### Fixed - *(oauth)* clear refresh marker on connection failures ([#664](#664)) - *(deps)* clear RUSTSEC-2026-0385 and RUSTSEC-2026-0387 ([#665](#665)) ### Other - *(deps)* update cargo minor updates ([#661](#661)) - *(deps)* update docker.io/grafana/otel-lgtm docker tag to v0.38.1 ([#662](#662)) - *(deps)* update docker.io/curlimages/curl docker tag to v8.23.0 ([#649](#649)) </blockquote> </p></details> --- This PR was generated with [release-plz](https://github.com/release-plz/release-plz/).
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.
What
The
cargo denyadvisories gate went red on two advisories published after thelast green run. No grob code pulled them in — they are transitive crypto crates,
so
mainfails the same check until this lands.ctutils0.4.2u128comparisonscrypto-bigint0.7.5crypto-bigint0.5.5The stuck 0.5.5
crypto-bigint 0.5.5is pulled unconditionally byage 0.12.1(the latestrelease) via its non-optional
hpke/p256 0.13→elliptic-curve 0.13.8dependencies. The advisory's fix (
>=0.7.6) covers only the 0.7.x line, and nogrob feature toggles this path off, so there is no upgrade path we control.
Per
deny.toml's own policy (prefer moving off an affected crate over anignore), moving off is not possible here, so it is ignored with a documented,
version-scoped entry and the review date is refreshed. The entry is scoped to
crypto-bigint@0.5.5specifically and should be removed the momentageshipsa release built on a fixed
crypto-bigint.Verification
cargo deny checkpasses locally with these changes (advisories/bans/licenses/sources all ok). Only
Cargo.lockanddeny.tomlchange; no source code.Closes #658
Closes #659
Closes #660
🤖 Generated with Claude Code