Vulnerability Database · OSS-Fuzz · Package report

wasmtime: vulnerability history, versions and safety

wasmtime is a package in the OSS-Fuzz ecosystem. Vulert records 10 vulnerabilities for it across 89 releases, from Jul 2022 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded H6 M1 U3
i
1 with no fix published

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

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

Most recent disclosure 21 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on wasmtime i

Updated on 23 Oct 2026

Careful: one of the 10 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 10 vulnerabilities on record across 3 years, 2 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 10 over 3 years · 2 in the last year i
  • Latest disclosure 21 Apr 2026 i
  • Highest CVSS n/a i
  • With no published fix 1 i

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 holds for wasmtime, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
dev H1 No Details →
v31.0.0 H1 No Details →
v30.0.2 H1 No Details →
v30.0.1 H1 No Details →
v30.0.0 H1 No Details →
v29.0.1 H1 No Details →
v29.0.0 H1 No Details →
v28.0.1 H1 No Details →
v28.0.0 H1 No Details →
v27.0.0 H1 No Details →
v26.0.1 H1 No Details →
v26.0.0 H1 No Details →
v25.0.3 H1 No Details →
v25.0.2 H1 No Details →
v25.0.1 H1 No Details →
v25.0.0 H1 No Details →
v24.0.2 H1 No Details →
v24.0.1 H1 No Details →
v24.0.0 H1 No Details →
v23.0.3 H1 No Details →
v23.0.2 H1 No Details →
v23.0.1 H1 No Details →
v23.0.0 H1 No Details →
v22.0.1 H1 No Details →
v22.0.0 H1 No Details →
v21.0.2 H1 No Details →
v21.0.1 H1 No Details →
v21.0.0 H1 No Details →
v20.0.2 H1 No Details →
v20.0.1 H1 No Details →
v20.0.0 H1 No Details →
v19.0.2 H1 No Details →
v19.0.1 H1 No Details →
v19.0.0 H1 No Details →
v18.0.4 H1 No Details →
v18.0.3 H1 No Details →
v18.0.2 H1 No Details →
v18.0.1 H1 No Details →
v18.0.0 H1 No Details →
v17.0.3 H1 No Details →
v17.0.2 H1 No Details →
v17.0.1 H1 No Details →
v17.0.0 H1 No Details →
v16.0.0 H1 No Details →
v15.0.1 H1 No Details →
v15.0.0 H1 No Details →
v14.0.4 H1 No Details →
v14.0.3 H1 No Details →
v14.0.2 H1 No Details →
v14.0.1 H1 No Details →
v14.0.0 H1 No Details →
v13.0.1 H1 No Details →
v13.0.0 H1 No Details →
v12.0.2 H1 No Details →
v12.0.1 H1 No Details →
v12.0.0 H1 No Details →
v11.0.2 H1 No Details →
v11.0.1 H1 No Details →
v11.0.0 H1 No Details →
v10.0.2 H1 No Details →
v10.0.1 H1 No Details →
v10.0.0 H1 No Details →
v9.0.4 H1 No Details →
v9.0.3 H1 No Details →
v9.0.2 H1 No Details →
v9.0.1 H1 No Details →
v9.0.0 H1 No Details →
v8.0.1 H1 No Details →
v8.0.0 H1 No Details →
v7.0.1 H1 No Details →
v7.0.0 H1 No Details →
v6.0.2 H1 No Details →
v6.0.1 H1 No Details →
v6.0.0 H1 No Details →
v5.0.1 H1 No Details →
v5.0.0 H1 No Details →
v4.0.1 H1 No Details →
v4.0.0 H1 No Details →
v3.0.1 H3 No Details →
v3.0.0 H3 No Details →
v2.0.2 H1 No Details →
v2.0.1 H1 No Details →
v2.0.0 H1 No Details →
v1.0.2 H1 No Details →
v1.0.1 H1 No Details →
v1.0.0 H1 No Details →
v0.40.1 H1 No Details →
v0.40.0 H1 No Details →
minimum-viable-wasi-proxy-serve H1 No Details →

Newest 89 of 89 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 7
  • 2024 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for wasmtime

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-use-after-free vulnerability in wasmtime N/A high No fix published 19 Jul 2022
Heap-use-after-free vulnerability in wasmtime N/A high 2154c63de94e0372bca5a596c3eaf90147c922d1 19 Jul 2022
Heap-use-after-free in .tmpoLlNv4 in wasmtime N/A high 2154c63de94e0372bca5a596c3eaf90147c922d1 19 Jul 2022
Segv on unknown address in cranelift_filetests::function_runner::CompiledFunction::call::ha6b9162cd2eNUMBER N/A unrated 573ae0c60bb20e010d74ba7fd2e7e59247f3385d 24 Aug 2022
Segv on unknown address in wasmtime_runtime::traphandlers::catch_traps::call_closure::hec711b3339636b04 N/A unrated dde2c5a3b6ee6caa1d597da0885613d2ce6a406a 26 Aug 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 wasmtime

Is wasmtime safe to use?

Vulert records 10 vulnerabilities for wasmtime in OSS-Fuzz: 0 critical, 6 high, 1 medium and 0 low, plus 3 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does wasmtime have?

10 vulnerabilities are recorded for wasmtime in the OSS-Fuzz ecosystem: 0 critical, 6 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 wasmtime vulnerabilities disclosed?

2 vulnerabilities were recorded for wasmtime in the last 12 months, and the oldest entry in this database dates to 19 Jul 2022. 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 wasmtime 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 wasmtime for upcoming vulnerabilities?

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