You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[DEP-02] Three concurrent rand major versions + RUSTSEC-2026-0097 across all of them #246
cargo audit reports RUSTSEC-2026-0097 (unsoundness when a custom logger calls rand::rng()) across all three. The unsoundness is real but not direct RCE; the bigger issue is security-critical code paths (crypto key gen vs identity) use non-interoperable rand majors.
Fix
Add rand = "0.9" to [workspace.dependencies] in the root Cargo.toml.
Switch crates/crypto and crates/identity to the workspace version.
Accept rand 0.10 in transitive rmcp path (MCP transport only, not key material) until rmcp upgrades.
Re-run cargo audit to confirm unsoundness advisory is no longer pinned to willow-authored crates.
Activity
ci(audit): ignore known RUSTSEC advisories tracked in separate issues
chore(skill): meta-tracker for structural-deps + re-grep at HEAD + me…
chore(skill): re-grep at HEAD + structural-deps meta-tracker
ci: ignore RUSTSEC-2026-0119 + 0120 (hickory-* via iroh)
docs(skill): retroactive meta-tracker fill-in during sweep
chore(ci): prune 3 stale RUSTSEC ignores from cargo-audit