CVE-2025-64345 Details
Description
Wasmtime is a runtime for WebAssembly. Prior to version 38.0.4, 37.0.3, 36.0.3, and 24.0.5, Wasmtime's Rust embedder API contains an unsound interaction where a WebAssembly shared linear memory could be viewed as a type which provides safe access to the host (Rust) to the contents of the linear memory. This is not sound for shared linear memories, which could be modified in parallel, and this could lead to a data race in the host. Patch releases have been issued for all supported versions of Wasmtime, notably: 24.0.5, 36.0.3, 37.0.3, and 38.0.4. These releases reject creation of shared memories via `Memory::new` and shared memories are now excluded from core dumps. As a workaround, eembeddings affected by this issue should use `SharedMemory::new` instead of `Memory::new` to create shared memories. Affected embeddings should also disable core dumps if they are unable to upgrade. Note that core dumps are disabled by default but the wasm threads proposal (and shared memory) is enabled by default.
A vulnerability exists in Wasmtime's Rust embedder API regarding the management of WebAssembly shared linear memory. In versions prior to 38.0.4, 37.0.3, 36.0.3, and 24.0.5, the API allowed shared linear memory to be represented as a type that provided safe access to its contents from the host. This representation is inherently unsafe, as shared memories can be modified concurrently, potentially leading to data races in the host environment. The issue arises because Wasmtime's `Memory` type, which is designed for non-shared memories, incorrectly allows the representation of shared linear memories. Embeddings that do not utilize the WebAssembly threads proposal or create shared memories are not affected.
Users should upgrade to Wasmtime versions 38.0.4, 37.0.3, 36.0.3, or 24.0.5, all of which include the necessary fix. After upgrading, shared memories should be created using the `SharedMemory::new` method instead of `Memory::new`. If an upgrade is not possible, core dumps can be disabled to prevent the unsynchronized read of shared memory.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Nov 12, 2025CISA-ADP
Assessed Nov 12, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| bytecodealliance wasmtime | <= 38.0.3 (semver) |
CPE
Remediation
| |
| bytecodealliance wasmtime::Memory | All versions |
CPE
Remediation
| |
| bytecodealliance wasmtime::SharedMemory | All versions |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 18, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 12, 2025 | New CVE Received | [email protected] |
Volerion