VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

im: vulnerability history, versions and safety

im is a package in the crates.io ecosystem. Vulert records 5 vulnerabilities for it across 36 releases, from Nov 2020 to May 2026. 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 M1 U4
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 03 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all im vulnerabilities

Vulert verdict on im 15.1.0 i

Updated on 23 Oct 2026

Careful: 15.1.0 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 15.1.0 — affected i
  • Vulnerabilities on record 5 over 5 years · 1 in the last year i
  • Latest disclosure 03 May 2026 i
  • Highest CVSS 4.7 i
  • With no published fix 2 i
  • Depended on by 638 packages i
  • Stars 1,583 i
  • OpenSSF scorecard 3/10 i
  • Last release 53 months ago i
  • Licence MPL-2.0+ 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 im, 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
15.1.0 29 Apr 2022 U2 MPL-2.0+ No Details →
15.0.0 15 May 2020 M1 U4 MPL-2.0+ No Details →
14.3.0 03 Mar 2020 M1 U4 MPL-2.0+ No Details →
14.2.0 17 Jan 2020 M1 U4 MPL-2.0+ No Details →
14.1.0 16 Dec 2019 M1 U4 MPL-2.0+ No Details →
14.0.0 19 Nov 2019 M1 U4 MPL-2.0+ No Details →
13.0.0 18 May 2019 M1 U4 MPL-2.0+ No Details →
12.3.4 08 Apr 2019 M1 U4 MPL-2.0+ No Details →
12.3.3 11 Mar 2019 M1 U4 MPL-2.0+ No Details →
12.3.2 05 Mar 2019 M1 U4 MPL-2.0+ No Details →
12.3.1 19 Feb 2019 M1 U4 MPL-2.0+ No Details →
12.3.0 15 Jan 2019 M1 U4 MPL-2.0+ No Details →
12.2.0 12 Oct 2018 M1 U4 MPL-2.0+ No Details →
12.1.0 25 Sep 2018 M1 U4 MPL-2.0+ No Details →
12.0.0 30 Aug 2018 M1 U4 MPL-2.0+ No Details →
11.0.2 30 Aug 2018 U2 MPL-2.0+ No Details →
11.0.1 23 Jul 2018 U2 MPL-2.0+ No Details →
11.0.0 10 Jul 2018 U2 MPL-2.0+ No Details →
10.2.0 15 Apr 2018 U2 MPL-2.0+ No Details →
10.1.0 12 Apr 2018 U2 MPL-2.0+ No Details →
10.0.0 06 Apr 2018 U2 MPL-2.0+ No Details →
9.0.0 07 Feb 2018 U2 LGPL-3.0+ No Details →
8.0.0 07 Jan 2018 U2 LGPL-3.0+ No Details →
7.1.0 07 Jan 2018 U2 LGPL-3.0+ No Details →
7.0.0 27 Sep 2017 U2 LGPL-3.0+ No Details →
6.0.0 01 Aug 2017 U2 LGPL-3.0+ No Details →
5.0.0 04 Jul 2017 U2 LGPL-3.0+ No Details →
4.1.0 02 Jul 2017 U2 LGPL-3.0+ No Details →
4.0.1 26 Jun 2017 U2 LGPL-3.0+ No Details →
4.0.0 26 Jun 2017 U2 LGPL-3.0+ No Details →
3.0.0 23 Jun 2017 U2 LGPL-3.0+ No Details →
2.0.3 17 Apr 2017 U2 LGPL-3.0+ No Details →
2.0.2 17 Apr 2017 U2 LGPL-3.0+ No Details →
2.0.1 17 Apr 2017 U2 LGPL-3.0+ No Details →
2.0.0 17 Apr 2017 U2 LGPL-3.0+ No Details →
1.0.0 17 Apr 2017 U2 LGPL-3.0+ No Details →

All 36 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
  • 2023 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for im

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-36204: Data races in im crate for Rust 4.7 medium 15.1.0 09 Nov 2020
CVE-2020-36204: Open Source Vulnerability in im Package - TreeFocus lacks bounds on its Send and Sync traits 4.7 medium 15.1.0 09 Nov 2020
CVE-2020-36204: Data races in im crate for Rust 4.7 medium 15.1.0 25 Aug 2021
Aliasing Violation in `im` Package: OrdSet Insertion Vulnerability N/A unrated No fix published 04 Feb 2023
Unmaintained Package Alert: im Crate Vulnerability N/A unrated No fix published 03 May 2026

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 im

Is im safe to use?

Vulert records 5 vulnerabilities for im in crates.io: 0 critical, 0 high, 1 medium and 0 low, plus 4 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is im's Vulert package health score?

Vulert scores im 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of im affected?

Yes. 15.1.0, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of im should I use?

15.1.0 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 im have?

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

1 vulnerability was recorded for im in the last 12 months, and the oldest entry in this database dates to 09 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 im 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 im for upcoming vulnerabilities?

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