Answer in brief
CVE-2022-39392 records a High severity (CVSS 7.4) vulnerability in Out of bounds read/write with zero-memory-pages configuration. The current sources do not mark it as known exploited. The current feed maps wasmtime (crates.io). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps wasmtime (crates.io). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| wasmtimecrates.io | >=0.0.0-0 <1.0.2 >=2.0.0 <2.0.2 | 1.0.2, 2.0.2 |
Published upstream
Nov 5, 2022
Evidence: source:osv:source_dates:source-dates:recordSource modified
Oct 12, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Oct 12, 2026
Bug in Wasmtime's implementation of its pooling instance allocator when the allocator is configured to give WebAssembly instances a maximum of zero pages of memory. In this configuration, the virtual memory mapping for WebAssembly memories did not meet the compiler-required configuration requirements for safely executing WebAssembly modules. Wasmtime's default settings require virtual memory page faults to indicate that wasm reads/writes are out-of-bounds, but the pooling allocator's configuration would not create an appropriate virtual memory mapping for this meaning out of bounds reads/writes can successfully read/write memory unrelated to the wasm sandbox within range of the base address of the memory mapping created by the pooling allocator. This bug is not applicable with the default settings of the `wasmtime` crate. This bug can only be triggered by setting `InstanceLimits::memory_pages` to zero. This is expected to be a very rare configuration since this means that wasm modules cannot allocate any pages of linear memory. All wasm modules produced by all current toolchains are highly likely to use linear memory, so it's expected to be unlikely that this configuration is set to zero by any production embedding of Wasmtime.
Quoted source text, attributed separately from HOL analysis.