VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

rand_core: vulnerability history, versions and safety

rand_core is a package in the crates.io ecosystem. Vulert records 5 vulnerabilities for it across 14 releases, from Apr 2019 to Aug 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C2 U3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all rand_core vulnerabilities

Vulert verdict on rand_core 0.10.1 i

Updated on 23 Oct 2026

Good news: 0.10.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on 0.10.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.10.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.10.1 — unaffected i
  • Vulnerabilities on record 5 over 2 years · 0 in the last year i
  • Latest disclosure 25 Aug 2021 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 1,584 packages i
  • Stars 2,085 i
  • Last release 6 months ago i
  • Licence Apache-2.0 OR MIT i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for rand_core, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.1.1 02 Sep 2026 U1 Apache-2.0 OR MIT Yes Details →
0.2.3 02 Sep 2026 U1 Apache-2.0 OR MIT Yes Details →
0.3.2 02 Sep 2026 none Apache-2.0 OR MIT — Details →
0.4.3 02 Sep 2026 none Apache-2.0 OR MIT — Details →
0.10.1 13 Apr 2026 none Apache-2.0 OR MIT — Details →
0.10.0 01 Feb 2026 none Apache-2.0 OR MIT — Details →
0.10.0-rc-6 24 Jan 2026 none Apache-2.0 OR MIT — Details →
0.10.0-rc-5 20 Jan 2026 none Apache-2.0 OR MIT — Details →
0.10.0-rc-4 19 Jan 2026 none Apache-2.0 OR MIT — Details →
0.9.5 13 Jan 2026 none Apache-2.0 OR MIT — Details →
0.9.4 12 Jan 2026 none Apache-2.0 OR MIT — Details →
0.10.0-rc-3 22 Dec 2025 none Apache-2.0 OR MIT — Details →
0.10.0-rc-2 31 Oct 2025 none Apache-2.0 OR MIT — Details →
0.10.0-rc-1 31 Oct 2025 none Apache-2.0 OR MIT — Details →
0.9.3 01 Mar 2025 none Apache-2.0 OR MIT — Details →
0.9.2 22 Feb 2025 none Apache-2.0 OR MIT — Details →
0.9.1 16 Feb 2025 none Apache-2.0 OR MIT — Details →
0.9.0 27 Jan 2025 none Apache-2.0 OR MIT — Details →
0.9.0-beta.1 30 Nov 2024 none Apache-2.0 OR MIT — Details →
0.9.0-beta.0 26 Nov 2024 none Apache-2.0 OR MIT — Details →
0.9.0-alpha.2 29 Jul 2024 none Apache-2.0 OR MIT — Details →
0.9.0-alpha.1 18 Mar 2024 none Apache-2.0 OR MIT — Details →
0.9.0-alpha.0 18 Feb 2024 none Apache-2.0 OR MIT — Details →
0.6.4 15 Sep 2022 none Apache-2.0 OR MIT — Details →
0.6.3 15 Jun 2021 none Apache-2.0 OR MIT — Details →
0.6.2 14 Feb 2021 none Apache-2.0 OR MIT — Details →
0.6.1 04 Jan 2021 C1 U2 Apache-2.0 OR MIT Yes Details →
0.6.0 14 Dec 2020 C1 U2 Apache-2.0 OR MIT Yes Details →
0.5.1 28 Aug 2019 none Apache-2.0 OR MIT — Details →
0.4.2 06 Aug 2019 none Apache-2.0 OR MIT — Details →
0.4.1 06 Jun 2019 C1 Apache-2.0 OR MIT Yes Details →
0.5.0 06 Jun 2019 none Apache-2.0 OR MIT — Details →
0.3.1 25 Jan 2019 none Apache-2.0 OR MIT — Details →
0.4.0 25 Jan 2019 C1 Apache-2.0 OR MIT Yes Details →
0.2.2 03 Oct 2018 U1 Apache-2.0 OR MIT Yes Details →
0.3.0 24 Sep 2018 U1 Apache-2.0 OR MIT Yes Details →
0.2.1 08 Jun 2018 U1 Apache-2.0 OR MIT Yes Details →
0.2.0 21 May 2018 U1 Apache-2.0 OR MIT Yes Details →
0.2.0-pre.0 15 May 2018 U1 Apache-2.0 OR MIT Yes Details →
0.1.0 17 Apr 2018 U1 Apache-2.0 OR MIT Yes Details →
0.1.0-pre.0 23 Mar 2018 U1 Apache-2.0 OR MIT Yes Details →
0.0.1 14 Sep 2017 U1 Apache-2.0 OR MIT Yes Details →

All 42 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2021 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for rand_core

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-25576: Unaligned memory access in rand_core 9.8 critical 0.4.2 25 Aug 2021
CVE-2021-27378: rand_core - Incorrect check on buffer length in rand_core 9.8 critical 0.6.2 12 Feb 2021
CVE-2020-25576: Unaligned memory access in rand_core 9.8 critical 0.3.1 19 Apr 2019
CVE-2021-27378: Incorrect check on buffer length when seeding RNGs in rand_core 9.8 critical 0.6.2 12 Feb 2021
CVE-2021-27378: Incorrect check on buffer length in rand_core 9.8 critical 0.6.2 25 Aug 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About rand_core

Is rand_core safe to use?

Vulert records 5 vulnerabilities for rand_core in crates.io: 2 critical, 0 high, 0 medium and 0 low, plus 3 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is rand_core's Vulert package health score?

Vulert scores rand_core 87/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of rand_core affected?

No. 0.10.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of rand_core should I use?

0.10.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does rand_core have?

5 vulnerabilities are recorded for rand_core in the crates.io ecosystem: 2 critical, 0 high, 0 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new rand_core vulnerabilities disclosed?

0 vulnerabilities were recorded for rand_core in the last 12 months, and the oldest entry in this database dates to 19 Apr 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of rand_core are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor rand_core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the rand_core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.