VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

mio: vulnerability history, versions and safety

mio is a package in the crates.io ecosystem. Vulert records 5 vulnerabilities for it across 26 releases, from Nov 2020 to Mar 2024. 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 H1 M1 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 mio vulnerabilities

Vulert verdict on mio 1.2.4 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 1.2.4 — unaffected i
  • Vulnerabilities on record 5 over 3 years · 0 in the last year i
  • Latest disclosure 04 Mar 2024 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 877 packages i
  • Stars 7,119 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence 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 mio, 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
1.2.4 03 Oct 2026 none MIT — Details →
1.2.3 02 Sep 2026 none MIT — Details →
1.2.2 13 Jul 2026 none MIT — Details →
1.2.1 28 May 2026 none MIT — Details →
1.2.0 27 Mar 2026 none MIT — Details →
1.1.1 04 Dec 2025 none MIT — Details →
1.1.0 17 Oct 2025 none MIT — Details →
1.0.4 24 May 2025 none MIT — Details →
1.0.3 29 Nov 2024 none MIT — Details →
1.0.2 12 Aug 2024 none MIT — Details →
1.0.1 23 Jul 2024 none MIT — Details →
1.0.0 14 Jun 2024 none MIT — Details →
0.8.11 01 Mar 2024 none MIT — Details →
0.8.10 06 Dec 2023 H1 U1 MIT Yes Details →
0.8.9 23 Oct 2023 H1 U1 MIT Yes Details →
0.8.8 30 May 2023 H1 U1 MIT Yes Details →
0.8.7 28 May 2023 H1 U1 MIT Yes Details →
0.8.6 14 Feb 2023 H1 U1 MIT Yes Details →
0.8.5 24 Oct 2022 H1 U1 MIT Yes Details →
0.8.4 19 Jun 2022 H1 U1 MIT Yes Details →
0.8.3 08 May 2022 H1 U1 MIT Yes Details →
0.8.2 17 Mar 2022 H1 U1 MIT Yes Details →
0.8.1 11 Mar 2022 H1 U1 MIT Yes Details →
0.8.0 13 Nov 2021 H1 U1 MIT Yes Details →
0.7.14 16 Oct 2021 H1 U1 MIT Yes Details →
0.7.13 14 Jun 2021 H1 U1 MIT Yes Details →
0.7.12 12 Jun 2021 H1 U1 MIT Yes Details →
0.7.11 22 Mar 2021 H1 U1 MIT Yes Details →
0.7.10 15 Mar 2021 H1 U1 MIT Yes Details →
0.7.9 22 Feb 2021 H1 U1 MIT Yes Details →
0.7.8 17 Feb 2021 H1 U1 MIT Yes Details →
0.7.7 30 Dec 2020 H1 U1 MIT Yes Details →
0.6.23 01 Dec 2020 none MIT — Details →
0.7.6 16 Nov 2020 H1 U1 MIT Yes Details →
0.7.5 31 Oct 2020 H1 M1 U3 MIT Yes Details →
0.7.4 20 Oct 2020 H1 M1 U3 MIT Yes Details →
0.7.3 07 Oct 2020 H1 M1 U3 MIT Yes Details →
0.7.2 02 Oct 2020 H1 M1 U3 MIT Yes Details →
0.7.1 29 Sep 2020 M1 U2 MIT Yes Details →
0.6.22 01 May 2020 none MIT — Details →
0.7.0 02 Mar 2020 M1 U2 MIT Yes Details →
0.7.0-alpha.1 17 Dec 2019 none MIT — Details →
0.6.21 27 Nov 2019 none MIT — Details →
0.6.20 22 Nov 2019 none MIT — Details →
0.6.19 28 May 2019 none MIT — Details →
0.6.18 24 May 2019 none MIT — Details →
0.6.17 15 May 2019 none MIT — Details →
0.6.16 05 Sep 2018 none MIT — Details →
0.6.15 03 Jul 2018 none MIT — Details →
0.6.14 08 Mar 2018 none MIT — Details →
0.6.13 06 Feb 2018 none MIT — Details →
0.6.12 06 Jan 2018 none MIT — Details →
0.6.11 25 Oct 2017 none MIT — Details →
0.6.10 31 Jul 2017 none MIT — Details →
0.6.9 07 Jun 2017 none MIT — Details →
0.6.8 26 May 2017 none MIT — Details →
0.6.7 27 Apr 2017 none MIT — Details →
0.6.6 22 Mar 2017 none MIT — Details →
0.6.5 15 Mar 2017 none MIT — Details →
0.6.4 24 Jan 2017 none MIT — Details →
0.6.3 22 Jan 2017 none MIT — Details →
0.6.2 18 Dec 2016 none MIT — Details →
0.6.1 31 Oct 2016 none MIT — Details →
0.6.0 02 Sep 2016 none MIT — Details →
0.5.1 27 Apr 2016 none MIT — Details →
0.5.0 04 Dec 2015 none MIT — Details →
0.4.4 05 Nov 2015 none MIT — Details →
0.4.3 31 Aug 2015 none MIT — Details →
0.4.2 17 Aug 2015 none MIT — Details →
0.4.1 21 Jul 2015 none MIT — Details →
0.4.0 16 Jul 2015 none MIT — Details →
0.3.7 09 Jul 2015 none MIT — Details →
0.3.6 12 Jun 2015 none MIT — Details →
0.3.5 13 May 2015 none MIT — Details →
0.3.4 22 Apr 2015 none MIT — Details →
0.3.3 12 Apr 2015 none MIT — Details →
0.3.2 07 Apr 2015 none MIT — Details →
0.3.1 02 Apr 2015 none MIT — Details →
0.3.0 30 Mar 2015 none MIT — Details →
0.2.1 18 Feb 2015 none — — Details →
0.1.0 11 Nov 2014 none — — Details →

All 81 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
  • 2024 2

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 mio

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-27308: Mio's tokens for named pipes may be delivered after deregistration 7.5 high 0.8.11 04 Mar 2024
CVE-2020-35922: Vulnerability in mio crate 5.5 medium 0.7.6 02 Nov 2020
CVE-2020-35922: Memory Access Vulnerability in mio 5.5 medium 0.7.6 02 Nov 2020
CVE-2020-35922: Vulnerability in mio crate 5.5 medium 0.7.6 25 Aug 2021
CVE-2024-27308: Vulnerability in mio package allows use-after-free in Tokio N/A unrated 0.8.11 04 Mar 2024

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 mio

Is mio safe to use?

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

Vulert scores mio 82/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 mio affected?

No. 1.2.4, 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 mio should I use?

1.2.4 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 mio have?

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

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

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