Skip to content

security(deps-tree): update rand to v0.8.6 [security]#88

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/crate-rand-vulnerability
Open

security(deps-tree): update rand to v0.8.6 [security]#88
renovate[bot] wants to merge 1 commit intomainfrom
renovate/crate-rand-vulnerability

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 14, 2026

This PR contains the following updates:

Package Type Update Change
rand (source) dependencies patch 0.8.50.8.6

Rand is unsound with a custom logger using rand::rng()

GHSA-cq8v-f236-94qc

More information

Details

It has been reported (by @​lopopolo) that the rand library is unsound (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:

  • The log and thread_rng features are enabled
  • A custom logger is defined
  • The custom logger accesses rand::rng() (previously rand::thread_rng()) and calls any TryRng (previously RngCore) methods on ThreadRng
  • The ThreadRng (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
  • Trace-level logging is enabled or warn-level logging is enabled and the random source (the getrandom crate) is unable to provide a new seed

TryRng (previously RngCore) methods for ThreadRng use unsafe code to cast *mut BlockRng<ReseedingCore> to &mut BlockRng<ReseedingCore>. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of aliased mutable references is Undefined Behaviour, the behaviour of optimized builds is hard to predict.

Severity

Low

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

rust-random/rand (rand)

v0.8.6

Compare Source

What's Changed

This release back-ports a fix from v0.10. See also #​1763.

Changes
  • Drop the experimental simd_support feature.

New Contributors

Full Changelog: rust-random/rand@0.8.5...0.8.6


Configuration

📅 Schedule: (in timezone Asia/Jakarta)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot requested a review from latipun7 as a code owner April 14, 2026 05:56
@renovate renovate Bot changed the title security(deps-tree): update rand to 0.9.0 [security] security(deps-tree): update rand to 0.9.0 [security] - autoclosed Apr 22, 2026
@renovate renovate Bot closed this Apr 22, 2026
@renovate renovate Bot deleted the renovate/crate-rand-vulnerability branch April 22, 2026 22:39
@renovate renovate Bot changed the title security(deps-tree): update rand to 0.9.0 [security] - autoclosed security(deps-tree): update rand to v0.8.6 [security] Apr 23, 2026
@renovate renovate Bot reopened this Apr 23, 2026
@renovate renovate Bot force-pushed the renovate/crate-rand-vulnerability branch 2 times, most recently from 071652a to f728250 Compare April 23, 2026 01:59
@renovate renovate Bot changed the title security(deps-tree): update rand to v0.8.6 [security] security(deps-tree): update rand to v0.8.6 [security] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title security(deps-tree): update rand to v0.8.6 [security] - autoclosed security(deps-tree): update rand to v0.8.6 [security] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate renovate Bot force-pushed the renovate/crate-rand-vulnerability branch 2 times, most recently from f728250 to 1f26f1c Compare April 27, 2026 23:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants