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

Source: https://junglewise.ai/threats/cve-2025-62711-wasmtime-vulnerable-to-segfault-when-using-component-resources  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-10-24  
License: CC BY 4.0 with a link back

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](https://junglewise.ai/threats/technologies/bytecodealliance-wasmtime), [wasmtime (crates.io)](https://junglewise.ai/threats/technologies/wasmtime). Vendors: [Bytecodealliance](https://junglewise.ai/threats/vendors/bytecodealliance), [crates.io](https://junglewise.ai/threats/vendors/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

  ```sh
  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

## Related threats

- [RUSTSEC-2026-0422 - Typed functions with `i31` or `nullref` arguments may panic due to insufficient type-check](https://junglewise.ai/threats/rustsec-2026-0422-typed-functions-with-i31-or-nullref-arguments-may-0545dc2b)
- [Wasmtime type confusion with host-created struct types](https://junglewise.ai/threats/rustsec-2026-0423-cross-engine-type-confusion-with-host-created-struct-89fe3f0e)
- [Wasmtime unchecked memory usage in borrowed resource transfer](https://junglewise.ai/threats/rustsec-2026-0424-unchecked-memory-usage-in-transferring-borrowed-b297503c)
- [Wasmtime Cranelift aarch64 br_table sandbox escape](https://junglewise.ai/threats/cve-2026-115893-wasmtime-is-a-runtime-for-webassembly-prior-to-36-0-19-48-0-7)
- [Wasmtime component-model type-check bypass in stream/future lowering](https://junglewise.ai/threats/cve-2026-115892-wasmtime-is-a-runtime-for-webassembly-from-46-0-0-until-48-0-7)