VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

tokio-rustls: vulnerability history, versions and safety

tokio-rustls is a package in the crates.io ecosystem. Vulert records 3 vulnerabilities for it across 3 releases, from May 2020 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
3 vulnerabilities recorded H1 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 tokio-rustls vulnerabilities

Vulert verdict on tokio-rustls 0.26.6 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Moderate

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

  • Current release 0.26.6 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 25 Aug 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 238 i
  • Last release this month 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 tokio-rustls, 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.26.6 28 Sep 2026 none Apache-2.0 OR MIT — Details →
0.26.5 04 Sep 2026 none Apache-2.0 OR MIT — Details →
0.26.4 26 Sep 2025 none Apache-2.0 OR MIT — Details →
0.26.3 17 Sep 2025 none Apache-2.0 OR MIT — Details →
0.26.2 01 Mar 2025 none Apache-2.0 OR MIT — Details →
0.26.1 05 Dec 2024 none Apache-2.0 OR MIT — Details →
0.26.0 22 Mar 2024 none Apache-2.0 OR MIT — Details →
0.25.0 05 Dec 2023 none Apache-2.0 OR MIT — Details →
0.25.0-alpha.4 30 Nov 2023 none Apache-2.0 OR MIT — Details →
0.25.0-alpha.3 26 Nov 2023 none Apache-2.0 OR MIT — Details →
0.25.0-alpha.2 22 Nov 2023 none Apache-2.0 OR MIT — Details →
0.25.0-alpha.1 23 Sep 2023 none Apache-2.0 OR MIT — Details →
0.24.1 09 Jun 2023 none Apache-2.0 OR MIT — Details →
0.24.0 31 Mar 2023 none Apache-2.0 OR MIT — Details →
0.23.4 04 May 2022 none Apache-2.0 OR MIT — Details →
0.23.3 19 Mar 2022 none Apache-2.0 OR MIT — Details →
0.23.2 16 Dec 2021 none Apache-2.0 OR MIT — Details →
0.23.1 30 Oct 2021 none Apache-2.0 OR MIT — Details →
0.23.0 15 Oct 2021 none Apache-2.0 OR MIT — Details →
0.22.0 24 Dec 2020 none Apache-2.0 OR MIT — Details →
0.21.1 09 Dec 2020 none Apache-2.0 OR MIT — Details →
0.15.0 25 Nov 2020 none Apache-2.0 OR MIT — Details →
0.21.0 25 Nov 2020 none Apache-2.0 OR MIT — Details →
0.20.0 16 Oct 2020 none Apache-2.0 OR MIT — Details →
0.14.1 31 Aug 2020 none Apache-2.0 OR MIT — Details →
0.14.0 05 Jul 2020 none Apache-2.0 OR MIT — Details →
0.12.3 19 May 2020 none Apache-2.0 OR MIT — Details →
0.13.1 19 May 2020 none Apache-2.0 OR MIT — Details →
0.13.0 23 Feb 2020 none Apache-2.0 OR MIT — Details →
0.12.2 07 Jan 2020 H1 U2 Apache-2.0 OR MIT Yes Details →
0.10.3 07 Jan 2020 none Apache-2.0 OR MIT — Details →
0.12.1 08 Dec 2019 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.0 27 Nov 2019 H1 U2 Apache-2.0 OR MIT Yes Details →
0.12.0-alpha.8 07 Nov 2019 none Apache-2.0 OR MIT — Details →
0.12.0-alpha.7 07 Nov 2019 none Apache-2.0 OR MIT — Details →
0.12.0-alpha.6 06 Nov 2019 none Apache-2.0 OR MIT — Details →
0.12.0-alpha.5 23 Oct 2019 none Apache-2.0 OR MIT — Details →
0.12.0-alpha.4 01 Oct 2019 none Apache-2.0 OR MIT — Details →
0.12.0-alpha.3 25 Sep 2019 none Apache-2.0 OR MIT — Details →
0.10.2 25 Sep 2019 none Apache-2.0 OR MIT — Details →
0.9.4 25 Sep 2019 none Apache-2.0 OR MIT — Details →
0.10.1 17 Sep 2019 none Apache-2.0 OR MIT — Details →
0.12.0-alpha.2 01 Sep 2019 none Apache-2.0 OR MIT — Details →
0.12.0-alpha.1 10 Aug 2019 none Apache-2.0 OR MIT — Details →
0.10.0 10 Aug 2019 none Apache-2.0 OR MIT — Details →
0.10.0-alpha.4 25 Jul 2019 none Apache-2.0 OR MIT — Details →
0.10.0-alpha.3 23 May 2019 none Apache-2.0 OR MIT — Details →
0.9.3 18 May 2019 none Apache-2.0 OR MIT — Details →
0.10.0-alpha.2 17 Apr 2019 none Apache-2.0 OR MIT — Details →
0.9.2 17 Apr 2019 none Apache-2.0 OR MIT — Details →
0.10.0-alpha.1 26 Mar 2019 none Apache-2.0 OR MIT — Details →
0.9.1 13 Mar 2019 none Apache-2.0 OR MIT — Details →
0.10.0-alpha 22 Feb 2019 none Apache-2.0 OR MIT — Details →
0.9.0 22 Jan 2019 none Apache-2.0 OR MIT — Details →
0.8.1 12 Jan 2019 none Apache-2.0 OR MIT — Details →
0.8.0 30 Sep 2018 none Apache-2.0 OR MIT — Details →
0.8.0-alpha 19 Sep 2018 none Apache-2.0 OR MIT — Details →
0.7.2 17 Aug 2018 none Apache-2.0 OR MIT — Details →
0.7.1 16 Jul 2018 none Apache-2.0 OR MIT — Details →
0.7.0 15 Jul 2018 none Apache-2.0 OR MIT — Details →
0.6.0 03 May 2018 none Apache-2.0 OR MIT — Details →
0.6.0-alpha.1 31 Mar 2018 none Apache-2.0 OR MIT — Details →
0.6.0-alpha 24 Mar 2018 none Apache-2.0 OR MIT — Details →
0.5.0 08 Jan 2018 none Apache-2.0 OR MIT — Details →
0.4.0 30 Aug 2017 none Apache-2.0 OR MIT — Details →
0.3.1 15 Aug 2017 none Apache-2.0 OR MIT — Details →
0.3.0 13 Aug 2017 none Apache-2.0 OR MIT — Details →
0.2.4 19 Jul 2017 none Apache-2.0 OR MIT — Details →
0.2.3 17 Jun 2017 none Apache-2.0 OR MIT — Details →
0.2.2 26 May 2017 none Apache-2.0 OR MIT — Details →
0.2.1 17 May 2017 none Apache-2.0 OR MIT — Details →
0.2.0 09 May 2017 none Apache-2.0 OR MIT — Details →
0.1.7 14 Apr 2017 none Apache-2.0 OR MIT — Details →
0.1.6 31 Mar 2017 none Apache-2.0 OR MIT — Details →
0.1.5 30 Mar 2017 none Apache-2.0 OR MIT — Details →
0.1.4 16 Mar 2017 none Apache-2.0 OR MIT — Details →
0.1.3 03 Mar 2017 none Apache-2.0 OR MIT — Details →
0.1.2 25 Feb 2017 none Apache-2.0 OR MIT — Details →
0.1.1 24 Feb 2017 none Apache-2.0 OR MIT — Details →
0.1.0 22 Feb 2017 none Apache-2.0 OR MIT — Details →

All 80 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
  • 2021 1

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

03 Vulnerabilities

Recorded vulnerabilities for tokio-rustls

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-35875: Excessive memory usage in tokio-rustls 7.5 high 0.12.3 19 May 2020
CVE-2020-35875: Excessive Memory Usage in tokio-rustls 7.5 high 0.12.3 19 May 2020
CVE-2020-35875: Excessive memory usage in tokio-rustls 7.5 high 0.12.3 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 tokio-rustls

Is tokio-rustls safe to use?

Vulert records 3 vulnerabilities for tokio-rustls in crates.io: 0 critical, 1 high, 0 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 tokio-rustls's Vulert package health score?

Vulert scores tokio-rustls 78/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 tokio-rustls affected?

No. 0.26.6, 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 tokio-rustls should I use?

0.26.6 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 tokio-rustls have?

3 vulnerabilities are recorded for tokio-rustls in the crates.io ecosystem: 0 critical, 1 high, 0 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 tokio-rustls vulnerabilities disclosed?

0 vulnerabilities were recorded for tokio-rustls in the last 12 months, and the oldest entry in this database dates to 19 May 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 tokio-rustls 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 tokio-rustls for upcoming vulnerabilities?

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