Skip to content

docs: [#444] mark RUSTSEC-2026-0097 resolved — rand 0.9.3 already in use #451

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
josecelano merged 1 commit into from
Apr 14, 2026
+8 −12
Merged

docs: [#444] mark RUSTSEC-2026-0097 resolved — rand 0.9.3 already in use #451

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 8 additions & 12 deletions docs/issues/444-rand-0.9.2-rustsec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,20 +45,16 @@ Expected `cargo audit` output: no finding for `rand 0.9.x`.

## Steps

- [ ] Run `cargo tree -p rand@0.9.3` — confirm it resolves without error
- [ ] Run `cargo audit` — confirm no finding for RUSTSEC-2026-0097 on rand 0.9.x
- [x] Run `cargo tree -p rand@0.9.3` — confirm it resolves without error
- [x] Run `cargo audit` — confirm no finding for RUSTSEC-2026-0097 on rand 0.9.x
- [ ] Post a comment on #444 with both outputs
- [ ] Close #444

## If the audit still reports rand 0.9.2

Run `cargo tree -i rand@0.9.2` to find which crate pins it, then apply
`cargo update rand` or bump that crate.

## Outcome

<!-- Fill in after doing the work -->

- Date:
- Result:
- Comment/PR:
- Date: 2026-04-14
- Result: **Resolved.** `cargo tree -p rand@0.9.3` resolves cleanly to `rand 0.9.3`
(patched). `cargo audit` reports only `rand 0.8.5` (tracked separately in #443)
— zero finding for `rand 0.9.x`. Issue #444 was opened before `Cargo.lock` was
updated to `rand 0.9.3`.
- Comment/PR: <!-- fill in after posting the comment and closing #444 -->
Loading