p PatchFirst

PatchFirst · Latest vulnerabilities

rust-wasmtime vulnerabilities · Page 2

Vulnerabilities published for rust-wasmtime in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 24

  1. CVE-2025-62711

    Low · CVSS 2.1EPSS 0.41%No fix published

    Wasmtime vulnerable to segfault when using component resources

    Wasmtime is a runtime for WebAssembly. In versions from 38.0.0 to before 38.0.3, the implementation of component-model related host-to-wasm trampolines in Wasmtime contained a bug where it's possible to carefully craft a component, which when called in a specific way, would crash the host with a segfault or assert failure. Wasmtime 38.0.3 has been released and is patched to fix this issue. There are no workarounds.

    Published Updated
  2. CVE-2025-53901

    Low · CVSS 3.5EPSS 0.38%No fix published

    Wasmtime has host panic with `fd_renumber` WASIp1 function

    Wasmtime is a runtime for WebAssembly. Prior to versions 24.0.4, 33.0.2, and 34.0.2, a bug in Wasmtime's implementation of the WASIp1 set of import functions can lead to a WebAssembly guest inducing a panic in the host (embedder). The specific bug is triggered by calling `path_open` after calling `fd_renumber` with either two equal argument values or a second argument being equal to a previously-closed file descriptor number value. The corrupt state introduced in `fd_renumber` will lead to the subsequent opening of a file descriptor to panic. This panic cannot introduce memory unsafety or allow WebAssembly to break outside of its sandbox, how

    Published Updated
  3. CVE-2024-47813

    Low · CVSS 2.9EPSS 0.15%No fix published

    Wasmtime race condition could lead to WebAssembly control-flow integrity and type safety violations

    Wasmtime is an open source runtime for WebAssembly. Under certain concurrent event orderings, a `wasmtime::Engine`'s internal type registry was susceptible to double-unregistration bugs due to a race condition, leading to panics and potentially type registry corruption. That registry corruption could, following an additional and particular sequence of concurrent events, lead to violations of WebAssembly's control-flow integrity (CFI) and type safety. Users that do not use `wasmtime::Engine` across multiple threads are not affected. Users that only create new modules across threads over time are additionally not affected. Reproducing this bug

    Published Updated
  4. CVE-2024-47763

    Medium · CVSS 5.5EPSS 0.24%No fix published

    Wasmtime runtime crash when combining tail calls with trapping imports

    Wasmtime is an open source runtime for WebAssembly. Wasmtime's implementation of WebAssembly tail calls combined with stack traces can result in a runtime crash in certain WebAssembly modules. The runtime crash may be undefined behavior if Wasmtime was compiled with Rust 1.80 or prior. The runtime crash is a deterministic process abort when Wasmtime is compiled with Rust 1.81 and later. WebAssembly tail calls are a proposal which relatively recently reached stage 4 in the standardization process. Wasmtime first enabled support for tail calls by default in Wasmtime 21.0.0, although that release contained a bug where it was only on-by-default f

    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →