Rust advisories / rand_os
UnmaintainedRUSTSEC-2025-0124 · rand_os
RUSTSEC-2025-0124: rand_os crate is unmaintained
Short answerNot a bug report: rand_os is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | rand_os |
|---|---|
| Type | Unmaintained |
| Affected versions | Every version. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2025-11-17 |
| Last changed | 2025-11-19 |
| Also known as | none |
What to do
- Look for a maintained fork or alternative crate.
- If you cannot move yet, acknowledge it in your audit config so CI stays green while you plan: add
"RUSTSEC-2025-0124"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i rand_os.
Details from the advisory
The rand_os crate is deprecated and no longer actively maintained, as OsRng is now part of rand_core.
If you are using this crate, consider upgrading to rand_core 0.5.1 or higher.
References
- Package: crates.io/crates/rand_os
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0124.html
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?