fix(security): Update Rust crate rand to 0.8.6 [SECURITY] #12

Merged

vxfemboy merged 1 commit from renovate/crate-rand-vulnerability into hellfire

2026-07-28 20:38:13 +00:00

noplife commented

2026-07-27 14:44:26 +00:00

Collaborator

This PR contains the following updates:

Package	Type	Update	Change
rand (source)	dependencies	patch	`0.8.5` → `0.8.6`

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

GHSA-cq8v-f236-94qc / RUSTSEC-2026-0097

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 OSV and the GitHub Advisory Database (CC-BY 4.0).

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

GHSA-cq8v-f236-94qc / RUSTSEC-2026-0097

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

Severity

Unknown

References

This data is provided by OSV and the Rust Advisory Database (CC0 1.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

Deprecate feature log (#1772)

Drop the experimental simd_support feature.

New Contributors

@nwalfield made their first contribution in #1772

Full Changelog: https://github.com/rust-random/rand/compare/0.8.5...0.8.6

Configuration

📅 Schedule: (UTC)

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 has been generated by Mend Renovate.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [rand](https://rust-random.github.io/book) ([source](https://github.com/rust-random/rand)) | dependencies | patch | `0.8.5` → `0.8.6` | --- ### Rand is unsound with a custom logger using rand::rng() [GHSA-cq8v-f236-94qc](https://github.com/advisories/GHSA-cq8v-f236-94qc) / [RUSTSEC-2026-0097](https://rustsec.org/advisories/RUSTSEC-2026-0097.html) <details> <summary>More information</summary> #### Details It has been reported (by @lopopolo) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (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](https://docs.rs/log/latest/log/#implementing-a-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](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict. #### Severity Low #### References - [https://github.com/rust-random/rand/pull/1763](https://github.com/rust-random/rand/pull/1763) - [https://github.com/rust-random/rand](https://github.com/rust-random/rand) - [https://rustsec.org/advisories/RUSTSEC-2026-0097.html](https://rustsec.org/advisories/RUSTSEC-2026-0097.html) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-cq8v-f236-94qc) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### Rand is unsound with a custom logger using `rand::rng()` [GHSA-cq8v-f236-94qc](https://github.com/advisories/GHSA-cq8v-f236-94qc) / [RUSTSEC-2026-0097](https://rustsec.org/advisories/RUSTSEC-2026-0097.html) <details> <summary>More information</summary> #### Details It has been reported (by [@lopopolo](https://github.com/lopopolo)) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (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](https://docs.rs/log/latest/log/#implementing-a-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](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict. #### Severity Unknown #### References - [https://crates.io/crates/rand](https://crates.io/crates/rand) - [https://rustsec.org/advisories/RUSTSEC-2026-0097.html](https://rustsec.org/advisories/RUSTSEC-2026-0097.html) - [https://github.com/rust-random/rand/pull/1763](https://github.com/rust-random/rand/pull/1763) This data is provided by [OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0097) and the [Rust Advisory Database](https://github.com/RustSec/advisory-db) ([CC0 1.0](https://github.com/rustsec/advisory-db/blob/main/LICENSE.txt)). </details> --- ### Release Notes <details> <summary>rust-random/rand (rand)</summary> ### [`v0.8.6`](https://github.com/rust-random/rand/releases/tag/0.8.6) [Compare Source](https://github.com/rust-random/rand/compare/0.8.5...0.8.6) #### What's Changed This release back-ports a fix from v0.10. See also [#1763]. ##### Changes - Deprecate feature `log` ([#1772]) [#1763]: https://github.com/rust-random/rand/pull/1763 [#1772]: https://github.com/rust-random/rand/pull/1772 - Drop the experimental `simd_support` feature. #### New Contributors - [@nwalfield](https://github.com/nwalfield) made their first contribution in [#1772](https://github.com/rust-random/rand/pull/1772) **Full Changelog**: <https://github.com/rust-random/rand/compare/0.8.5...0.8.6> </details> --- ### Configuration 📅 **Schedule**: (UTC) - 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 has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).

noplife added 1 commit

2026-07-27 14:44:26 +00:00

fix(security): Update Rust crate rand to 0.8.6 [SECURITY] 6c10344e8b