Vulnerability Database · crates.io · wasmtime · Version
wasmtime 36.0.7
36.0.7 is affected by 6 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 2 High 0 Medium 3 Low 1 Unrated 0
-
Released 09 Apr 2026
Licence Apache-2.0 WITH LLVM-exception
Also known from other sources 17
Newer releases 234
Database updated 23/Oct/2026
Release and licence data published by crates.io. 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 Vulnerabilities affecting this version
wasmtime 36.0.7 vulnerabilities
6 vulnerabilities cover wasmtime 36.0.7. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Critical Vulnerability in Wasmtime: Incorrect Jump Target on Large Wasm br_table Instruction | 9.9 critical | 36.0.19 | 19 Oct 2026 |
| Critical Bit-Packing Overflow in Wasmtime Compiler | 9.9 critical | 36.0.19 | 19 Oct 2026 |
| Wasmtime Package Vulnerability: Component-Model Handle Tables Capped Per Instance | 6.2 medium | 36.0.18 | 14 Oct 2026 |
| CVE-2026-44216: Wasmtime Denial-of-Service Vulnerability Due to Table Allocation Panic | 5.9 medium | 36.0.8 | 07 May 2026 |
| Critical Memory Allocation Panic in Wasmtime Package | 5.9 medium | 36.0.8 | 30 Apr 2026 |
| Dynamic Record Lifting Vulnerability in Wasmtime: Allocation Beyond Hostcall Fuel Limit | 1.0 low | 36.0.16 | 24 Sep 2026 |
Looking for another version, or everything Vulert holds for wasmtime?
Questions
About wasmtime 36.0.7
Is wasmtime 36.0.7 vulnerable?
Yes. 6 vulnerabilities in the Vulert database cover wasmtime 36.0.7: 2 critical, 0 high, 3 medium and 1 low. Each entry above names the fixed version to move to.
Is 36.0.7 the latest release of wasmtime?
No. 36.0.7 was published 09 Apr 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.