VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

futures-util: vulnerability history, versions and safety

futures-util is a package in the crates.io ecosystem. Vulert records 4 vulnerabilities for it across 7 releases, from Jan 2020 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M2 U2
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 futures-util vulnerabilities

Vulert verdict on futures-util 0.3.34 i

Updated on 23 Oct 2026

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

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

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

  • Current release 0.3.34 — unaffected i
  • Vulnerabilities on record 4 over 2 years · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 5.5 i
  • With no published fix 0 i
  • Depended on by 27,910 packages i
  • Stars 5,934 i
  • OpenSSF scorecard 5/10 i
  • Last release 2 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 futures-util, 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.3.34 11 Aug 2026 none Apache-2.0 OR MIT — Details →
0.3.33 18 Jul 2026 none Apache-2.0 OR MIT — Details →
0.3.32 15 Feb 2026 none Apache-2.0 OR MIT — Details →
0.3.31 05 Oct 2024 none Apache-2.0 OR MIT — Details →
0.3.30 24 Dec 2023 none Apache-2.0 OR MIT — Details →
0.3.29 26 Oct 2023 none Apache-2.0 OR MIT — Details →
0.3.28 30 Mar 2023 none Apache-2.0 OR MIT — Details →
0.3.27 11 Mar 2023 none Apache-2.0 OR MIT — Details →
0.3.26 30 Jan 2023 none Apache-2.0 OR MIT — Details →
0.3.25 20 Oct 2022 none Apache-2.0 OR MIT — Details →
0.3.24 29 Aug 2022 none Apache-2.0 OR MIT — Details →
0.3.23 14 Aug 2022 none Apache-2.0 OR MIT — Details →
0.3.22 14 Aug 2022 none Apache-2.0 OR MIT — Details →
0.3.21 06 Feb 2022 none Apache-2.0 OR MIT — Details →
0.3.20 06 Feb 2022 none Apache-2.0 OR MIT — Details →
0.3.19 18 Dec 2021 none Apache-2.0 OR MIT — Details →
0.3.18 23 Nov 2021 none Apache-2.0 OR MIT — Details →
0.3.17 30 Aug 2021 none Apache-2.0 OR MIT — Details →
0.3.16 23 Jul 2021 none Apache-2.0 OR MIT — Details →
0.3.15 11 May 2021 none Apache-2.0 OR MIT — Details →
0.3.14 10 Apr 2021 none Apache-2.0 OR MIT — Details →
0.3.13 23 Feb 2021 none Apache-2.0 OR MIT — Details →
0.3.12 15 Jan 2021 none Apache-2.0 OR MIT — Details →
0.3.11 14 Jan 2021 none Apache-2.0 OR MIT — Details →
0.3.10 13 Jan 2021 none Apache-2.0 OR MIT — Details →
0.3.9 08 Jan 2021 none Apache-2.0 OR MIT — Details →
0.3.8 09 Nov 2020 none Apache-2.0 OR MIT — Details →
0.3.7 23 Oct 2020 none Apache-2.0 OR MIT — Details →
0.3.6 05 Oct 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.3.5 08 May 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.3.4 07 Feb 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.3.3 05 Feb 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.3.2 04 Feb 2020 M1 U1 Apache-2.0 OR MIT Yes Details →
0.3.1 07 Nov 2019 M1 U1 Apache-2.0 OR MIT Yes Details →
0.3.0 06 Nov 2019 M1 U1 Apache-2.0 OR MIT Yes Details →
0.2.1 19 Apr 2018 none Apache-2.0 OR MIT — Details →
0.2.0 06 Apr 2018 none Apache-2.0 OR MIT — Details →
0.2.0-beta 20 Mar 2018 none Apache-2.0 OR MIT — Details →
0.2.0-alpha 05 Mar 2018 none Apache-2.0 OR MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for futures-util

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-35908: Improper Sync implementation on FuturesUnordered in futures-util can cause data corruption 5.5 medium 0.3.2 24 Jan 2020
CVE-2020-35908: Improper `Sync` implementation on `FuturesUnordered` in futures-utils can cause data corruption 5.5 medium 0.3.2 24 May 2022
CVE-2020-35905: MutexGuard::map Data Race Vulnerability in futures-util 4.7 medium 0.3.7 22 Oct 2020
CVE-2020-35905: MutexGuard::map can cause a data race in safe code in futures-util 4.7 medium 0.3.7 24 May 2022

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 futures-util

Is futures-util safe to use?

Vulert records 4 vulnerabilities for futures-util in crates.io: 0 critical, 0 high, 2 medium and 0 low, plus 2 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 futures-util's Vulert package health score?

Vulert scores futures-util 88/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 futures-util affected?

No. 0.3.34, 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 futures-util should I use?

0.3.34 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 futures-util have?

4 vulnerabilities are recorded for futures-util in the crates.io ecosystem: 0 critical, 0 high, 2 medium and 0 low, plus 2 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 futures-util vulnerabilities disclosed?

0 vulnerabilities were recorded for futures-util in the last 12 months, and the oldest entry in this database dates to 24 Jan 2020. 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 futures-util 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 futures-util for upcoming vulnerabilities?

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