VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

wasmer: vulnerability history, versions and safety

wasmer is a package in the crates.io ecosystem. Vulert records 1 vulnerability for it across 114 releases, first recorded in Jun 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded L1
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 wasmer vulnerabilities

Vulert verdict on wasmer 7.5.0 i

Updated on 23 Oct 2026

Careful: 7.5.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

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 7.5.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 07 Jun 2024 i
  • Highest CVSS 2.9 i
  • With no published fix 1 i
  • Stars 21,167 i
  • OpenSSF scorecard 5/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 wasmer, 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
7.5.0 01 Oct 2026 L1 MIT No Details →
7.5.0-rc.2 01 Oct 2026 L1 MIT No Details →
7.5.0-rc.1 30 Sep 2026 L1 MIT No Details →
7.4.1 15 Sep 2026 L1 MIT No Details →
7.4.2 15 Sep 2026 L1 MIT No Details →
7.4.0 31 Aug 2026 L1 MIT No Details →
7.3.0 21 Aug 2026 L1 MIT No Details →
7.3.0-rc.1 21 Aug 2026 L1 MIT No Details →
7.2.1 27 Jul 2026 L1 MIT No Details →
7.2.0 30 Jun 2026 L1 MIT No Details →
7.2.0-rc.1 29 Jun 2026 L1 MIT No Details →
7.2.0-alpha.3 01 Jun 2026 L1 MIT No Details →
7.2.0-alpha.2 24 Apr 2026 L1 MIT No Details →
7.2.0-alpha.1 10 Apr 2026 L1 MIT No Details →
7.1.0 27 Mar 2026 L1 MIT No Details →
7.1.0-rc.3 27 Mar 2026 L1 MIT No Details →
7.1.0-rc.2 17 Mar 2026 L1 MIT No Details →
7.1.0-rc.1 16 Mar 2026 L1 MIT No Details →
7.1.0-alpha.1 24 Feb 2026 L1 MIT No Details →
7.0.1 02 Feb 2026 L1 MIT No Details →
7.0.0 28 Jan 2026 L1 MIT No Details →
7.0.0-rc.2 27 Jan 2026 L1 MIT No Details →
7.0.0-rc.1 23 Jan 2026 L1 MIT No Details →
7.0.0-alpha.2 13 Jan 2026 L1 MIT No Details →
6.1.0 08 Oct 2025 L1 MIT No Details →
6.1.0-rc.5 17 Sep 2025 L1 MIT No Details →
6.1.0-rc.3 20 Aug 2025 L1 MIT No Details →
6.1.0-rc.2 17 Jul 2025 L1 MIT No Details →
6.0.1 09 May 2025 L1 MIT No Details →
5.0.6 02 May 2025 L1 MIT No Details →
6.0.0 24 Apr 2025 L1 MIT No Details →
6.0.0-beta.1 07 Mar 2025 L1 MIT No Details →
6.0.0-alpha.2 26 Feb 2025 L1 MIT No Details →
6.0.0-alpha.1 18 Feb 2025 L1 MIT No Details →
5.0.5-rc1 03 Jan 2025 L1 MIT No Details →
5.0.4 17 Dec 2024 L1 MIT No Details →
5.0.3 07 Dec 2024 L1 MIT No Details →
5.0.2 25 Nov 2024 L1 MIT No Details →
5.0.1 06 Nov 2024 L1 MIT No Details →
5.0.0 29 Oct 2024 L1 MIT No Details →
5.0.0-rc.1 21 Oct 2024 L1 MIT No Details →
4.4.0 04 Oct 2024 L1 MIT No Details →
4.3.7 09 Sep 2024 L1 MIT No Details →
4.3.6 22 Aug 2024 L1 MIT No Details →
4.3.5 16 Jul 2024 L1 MIT No Details →
4.3.4 08 Jul 2024 L1 MIT No Details →
4.3.3 04 Jul 2024 L1 MIT No Details →
4.3.2 11 Jun 2024 L1 MIT No Details →
4.3.1 23 May 2024 L1 MIT No Details →
4.3.0 10 May 2024 L1 MIT No Details →
4.3.0-beta.1 08 May 2024 L1 MIT No Details →
4.3.0-alpha.1 25 Apr 2024 L1 MIT No Details →
4.2.8 08 Apr 2024 L1 MIT No Details →
4.2.6 04 Mar 2024 L1 MIT No Details →
4.2.5 23 Dec 2023 L1 MIT No Details →
4.2.4 01 Dec 2023 L1 MIT No Details →
4.2.3 27 Oct 2023 L1 MIT No Details →
4.2.2 05 Oct 2023 L1 MIT No Details →
4.2.1 28 Sep 2023 L1 MIT No Details →
4.2.0 05 Sep 2023 L1 MIT No Details →
4.1.2 21 Aug 2023 L1 MIT No Details →
4.1.1 03 Aug 2023 L1 MIT No Details →
4.1.0 24 Jul 2023 L1 MIT No Details →
4.0.0 22 Jun 2023 L1 MIT No Details →
4.0.0-beta.3 15 Jun 2023 L1 MIT No Details →
4.0.0-beta.2 09 Jun 2023 L1 MIT No Details →
4.0.0-beta.1 01 Jun 2023 L1 MIT No Details →
4.0.0-alpha.1 25 May 2023 L1 MIT No Details →
3.3.0 03 May 2023 L1 MIT No Details →
3.2.1 21 Apr 2023 L1 MIT No Details →
3.2.0 18 Apr 2023 L1 MIT No Details →
3.2.0-beta.2 05 Apr 2023 L1 MIT No Details →
3.2.0-beta.1 23 Mar 2023 L1 MIT No Details →
3.1.1 26 Jan 2023 L1 MIT No Details →
3.0.3 26 Jan 2023 L1 MIT No Details →
3.2.0-alpha.1 23 Jan 2023 L1 MIT No Details →
3.1.0 12 Dec 2022 L1 MIT No Details →
3.0.2 27 Nov 2022 L1 MIT No Details →
3.0.1 23 Nov 2022 L1 MIT No Details →
3.0.0 20 Nov 2022 L1 MIT No Details →
3.0.0-rc.4 19 Nov 2022 L1 MIT No Details →
3.0.0-rc.3 18 Nov 2022 L1 MIT No Details →
3.0.0-rc.2 02 Nov 2022 L1 MIT No Details →
3.0.0-rc.1 25 Oct 2022 L1 MIT No Details →
3.0.0-beta.2 27 Sep 2022 L1 MIT No Details →
3.0.0-beta 08 Aug 2022 L1 MIT No Details →
3.0.0-alpha.4 29 Jul 2022 L1 MIT No Details →
3.0.0-alpha.3 28 Jul 2022 L1 MIT No Details →
3.0.0-alpha.2 28 Jul 2022 L1 MIT No Details →
3.0.0-alpha 28 Jul 2022 L1 MIT No Details →
2.3.0 06 Jun 2022 L1 MIT No Details →
2.2.1 16 Mar 2022 L1 MIT No Details →
2.2.0 28 Feb 2022 L1 MIT No Details →
2.2.0-rc2 17 Feb 2022 L1 MIT No Details →
2.2.0-rc1 28 Jan 2022 L1 MIT No Details →
2.1.1 21 Dec 2021 L1 MIT No Details →
2.1.0 30 Nov 2021 L1 MIT No Details →
2.0.0 16 Jun 2021 L1 MIT No Details →
2.0.0-rc2 15 Jun 2021 L1 MIT No Details →
2.0.0-rc1 02 Jun 2021 L1 MIT No Details →
1.0.2 05 Feb 2021 L1 — No Details →
1.0.1 13 Jan 2021 L1 — No Details →
1.0.0 05 Jan 2021 L1 — No Details →
1.0.0-rc1 23 Dec 2020 L1 — No Details →
1.0.0-beta2 16 Dec 2020 L1 — No Details →
1.0.0-beta1 02 Dec 2020 L1 — No Details →
1.0.0-alpha5 06 Nov 2020 L1 — No Details →
1.0.0-alpha4 09 Oct 2020 L1 — No Details →
1.0.0-alpha3 14 Sep 2020 L1 — No Details →
1.0.0-alpha02.0 11 Sep 2020 L1 — No Details →
1.0.0-alpha01.0 15 Aug 2020 L1 — No Details →
0.17.1 24 Jun 2020 L1 — No Details →
0.17.0 11 May 2020 L1 — No Details →
0.1.0 24 Oct 2018 L1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for wasmer

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-38358: Symlink bypasses filesystem sandbox in wasmer 2.9 low No fix published 07 Jun 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 wasmer

Is wasmer safe to use?

Vulert records 1 vulnerabilities for wasmer in crates.io: 0 critical, 0 high, 0 medium and 1 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is wasmer's Vulert package health score?

Vulert scores wasmer 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 wasmer affected?

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

Which version of wasmer should I use?

7.5.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 wasmer have?

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

How often are new wasmer vulnerabilities disclosed?

0 vulnerabilities were recorded for wasmer in the last 12 months, and the oldest entry in this database dates to 07 Jun 2024. 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 wasmer 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 wasmer for upcoming vulnerabilities?

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