VulertSecurity VulertSecurity

Vulnerability Database · crates.io · wasmtime · Version

wasmtime 30.0.0

30.0.0 is affected by 19 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 5 High 0 Medium 9 Low 5 Unrated 0

All wasmtime versions & vulnerabilities → Search the database for this package →
Released 20 Feb 2025 Licence Apache-2.0 WITH LLVM-exception Also known from other sources 0 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 30.0.0 vulnerabilities

19 vulnerabilities cover wasmtime 30.0.0. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
Critical Bit-Packing Overflow in Wasmtime Compiler 9.9 critical 36.0.19 19 Oct 2026
Critical Vulnerability in Wasmtime: Incorrect Jump Target on Large Wasm br_table Instruction 9.9 critical 36.0.19 19 Oct 2026
CVE-2026-34987: Wasmtime Package Vulnerability Allows Sandbox-Escaping Memory Access 9.2 critical 36.0.7 10 Apr 2026
CVE-2026-34987: Wasmtime Package Vulnerability Allows Sandbox-Escaping Memory Access 9.0 critical 36.0.7 09 Apr 2026
CVE-2026-34971: Wasmtime Package Miscompiled Guest Heap Access Vulnerability 9.0 critical 36.0.7 09 Apr 2026
Wasmtime Package Vulnerability: Component-Model Handle Tables Capped Per Instance 6.2 medium 36.0.18 14 Oct 2026
CVE-2026-35186: Wasmtime Improperly Masks Return Value from table.grow in Winch Compiler Backend 6.1 medium 36.0.7 10 Apr 2026
CVE-2026-35186: Wasmtime Package - Improperly Masked Return Value Vulnerability 6.1 medium 36.0.7 09 Apr 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
CVE-2026-34946: Wasmtime Denial-of-Service Vulnerability via Host Panic on `table.fill` Execution 5.9 medium 36.0.7 09 Apr 2026
CVE-2026-34946: Wasmtime Host Panic Due to `table.fill` Execution 5.9 medium 36.0.7 09 Apr 2026
CVE-2026-24116: Wasmtime Segfault or Unused Out-of-Sandbox Load with f64.copysign Operator on x86-64 4.1 medium 36.0.5 27 Jan 2026
Segmentation Fault Risk in Wasmtime with f64.copysign on x86-64 4.1 medium 36.0.5 26 Jan 2026
CVE-2026-34988: Wasmtime Pooling Allocator Data Leakage Vulnerability 2.3 low 36.0.7 09 Apr 2026
CVE-2026-34945: Wasmtime 64-bit Table Host Data Leakage Vulnerability 2.3 low 36.0.7 09 Apr 2026
CVE-2026-34945: Wasmtime Host Data Leakage Vulnerability 2.3 low 36.0.7 09 Apr 2026
CVE-2026-34988: Wasmtime Data Leakage Between Pooling Allocator Instances 2.3 low 36.0.7 09 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?

All versions → Full vulnerability list →

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 30.0.0

Is wasmtime 30.0.0 vulnerable?

Yes. 19 vulnerabilities in the Vulert database cover wasmtime 30.0.0: 5 critical, 0 high, 9 medium and 5 low. Each entry above names the fixed version to move to.

Is 30.0.0 the latest release of wasmtime?

No. 30.0.0 was published 20 Feb 2025, 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.