VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

getrandom: vulnerability history, versions and safety

getrandom is a package in the crates.io ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the crates.io ecosystem.

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 getrandom vulnerabilities

Vulert verdict on getrandom 0.4.3 i

Updated on 23 Oct 2026

Good news: 0.4.3, the version you would install today, has no known vulnerabilities.

Package health score 84/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 0.4.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 13,866 packages i
  • Stars 590 i
  • OpenSSF scorecard 6/10 i
  • Last release 4 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 getrandom, 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.4.3 17 Jun 2026 none Apache-2.0 OR MIT — Details →
0.4.2 03 Mar 2026 none Apache-2.0 OR MIT — Details →
0.4.1 03 Feb 2026 none Apache-2.0 OR MIT — Details →
0.4.0 02 Feb 2026 none Apache-2.0 OR MIT — Details →
0.4.0-rc.1 24 Jan 2026 none Apache-2.0 OR MIT — Details →
0.2.17 11 Jan 2026 none Apache-2.0 OR MIT — Details →
0.4.0-rc.0 27 Dec 2025 none Apache-2.0 OR MIT — Details →
0.3.4 14 Oct 2025 none Apache-2.0 OR MIT — Details →
0.3.3 09 May 2025 none Apache-2.0 OR MIT — Details →
0.2.16 22 Apr 2025 none Apache-2.0 OR MIT — Details →
0.3.2 17 Mar 2025 none Apache-2.0 OR MIT — Details →
0.3.1 28 Jan 2025 none Apache-2.0 OR MIT — Details →
0.3.0 25 Jan 2025 none Apache-2.0 OR MIT — Details →
0.3.0-rc.0 29 Nov 2024 none Apache-2.0 OR MIT — Details →
0.2.15 06 May 2024 none Apache-2.0 OR MIT — Details →
0.2.14 08 Apr 2024 none Apache-2.0 OR MIT — Details →
0.2.13 06 Apr 2024 none Apache-2.0 OR MIT — Details →
0.2.12 09 Jan 2024 none Apache-2.0 OR MIT — Details →
0.2.11 08 Nov 2023 none Apache-2.0 OR MIT — Details →
0.2.10 06 Jun 2023 none Apache-2.0 OR MIT — Details →
0.2.9 06 Apr 2023 none Apache-2.0 OR MIT — Details →
0.2.8 20 Oct 2022 none Apache-2.0 OR MIT — Details →
0.2.7 14 Jun 2022 none Apache-2.0 OR MIT — Details →
0.2.6 28 Mar 2022 none Apache-2.0 OR MIT — Details →
0.2.5 22 Feb 2022 none Apache-2.0 OR MIT — Details →
0.2.4 13 Jan 2022 none Apache-2.0 OR MIT — Details →
0.2.3 20 May 2021 none Apache-2.0 OR MIT — Details →
0.2.2 19 Jan 2021 none Apache-2.0 OR MIT — Details →
0.2.1 04 Jan 2021 none Apache-2.0 OR MIT — Details →
0.1.16 31 Dec 2020 none Apache-2.0 OR MIT — Details →
0.2.0 10 Sep 2020 none Apache-2.0 OR MIT — Details →
0.1.15 10 Sep 2020 none Apache-2.0 OR MIT — Details →
0.1.14 07 Jan 2020 none Apache-2.0 OR MIT — Details →
0.1.13 25 Oct 2019 none Apache-2.0 OR MIT — Details →
0.1.12 06 Sep 2019 none Apache-2.0 OR MIT — Details →
0.1.11 25 Aug 2019 none Apache-2.0 OR MIT — Details →
0.1.10 17 Aug 2019 none Apache-2.0 OR MIT — Details →
0.1.9 14 Aug 2019 none Apache-2.0 OR MIT — Details →
0.1.8 05 Aug 2019 none Apache-2.0 OR MIT — Details →
0.1.7 29 Jul 2019 none Apache-2.0 OR MIT — Details →
0.1.6 30 Jun 2019 none Apache-2.0 OR MIT — Details →
0.1.5 29 Jun 2019 none Apache-2.0 OR MIT — Details →
0.1.4 28 Jun 2019 none Apache-2.0 OR MIT — Details →
0.1.3 17 May 2019 none Apache-2.0 OR MIT — Details →
0.1.2 06 Apr 2019 none Apache-2.0 OR MIT — Details →
0.1.1 05 Apr 2019 none Apache-2.0 OR MIT — Details →
0.1.0 23 Mar 2019 none Apache-2.0 OR MIT — Details →
0.0.0 19 Jan 2019 none Apache-2.0 OR MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for getrandom

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 getrandom

Is getrandom safe to use?

Vulert has no vulnerabilities on record for getrandom in crates.io at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is getrandom's Vulert package health score?

Vulert scores getrandom 84/100, which reads as in good shape. 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 getrandom affected?

No. 0.4.3, 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 getrandom should I use?

0.4.3 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 getrandom have?

0 vulnerabilities are recorded for getrandom in the crates.io ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new getrandom vulnerabilities disclosed?

0 vulnerabilities were recorded for getrandom in the last 12 months. 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 getrandom 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 getrandom for upcoming vulnerabilities?

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