CVE-2025-62711: RUSTSEC-2025-0112 - Possible host crash with host-to-wasm component intrinsics

CVE-2025-62711 · Severity: medium · CVSS 4 · Published 2025-10-24

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.

Technologies: Bytecodealliance Wasmtime, wasmtime (crates.io). Vendors: Bytecodealliance, crates.io.

Quick answers

Is CVE-2025-62711 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-62711 being exploited in the wild.
How severe is CVE-2025-62711?
Medium severity, with a CVSS score of 4, published 24 October 2025.
Which products and versions are affected?
wasmtime (crates.io) SEMVER:introduced=38.0.0,fixed=38.0.3.
Is there a fix for CVE-2025-62711?
Yes. wasmtime (crates.io): upgrade to 38.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-62711?
Check whether you run Bytecodealliance Wasmtime or wasmtime (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • wasmtime (crates.io): upgrade to 38.0.3 or later
    cargo update -p wasmtime

Affected products

  • Bytecodealliance Wasmtime
  • wasmtime (crates.io) SEMVER:introduced=38.0.0,fixed=38.0.3

Identifiers

  • CVE-2025-62711
  • GHSA-4h67-722j-5pmc
  • RUSTSEC-2025-0112

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.