Vulnerability LowRUSTSEC-2022-0097 · wasmtime
RUSTSEC-2022-0097: Out of bounds write in `wasmtime_trap_code` C API function
Short answerA security vulnerability in the wasmtime crate: Out of bounds write in `wasmtime_trap_code` C API function. Low severity (CVSS 3.8). Fixed in 1.0.2, 2.0.2: update to a fixed version.
| Crate | wasmtime |
|---|---|
| Type | Vulnerability |
| Affected versions | Before 1.0.2; from 2.0.0 before 2.0.2. |
| Fixed in | 1.0.2, 2.0.2 |
| Severity | Low, CVSS 3.8 CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L |
| Published | 2022-11-07 |
| Last changed | 2026-10-12 |
| Also known as | CVE-2022-39394, GHSA-h84q-m8rr-3v9q |
What to do
- See which version you have:
cargo tree -i wasmtime(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p wasmtime. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplewasmtime = "2.0.2") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-h84q-m8rr-3v9q. For more information see the GitHub-hosted security advisory.
References
- Package: crates.io/crates/wasmtime
- Advisory: rustsec.org/advisories/RUSTSEC-2022-0097.html
- Web: github.com/bytecodealliance/wasmtime/commit/087d9d7becf7422b3f872a3bcd5d97bb7ce7ff36
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for wasmtime
- Vulnerability MediumRUSTSEC-2021-0110 · 2021-09-17Multiple Vulnerabilities in Wasmtime
- VulnerabilityRUSTSEC-2022-0016 · 2022-03-31Use after free with `externref`s and epoch interruption in Wasmtime
- VulnerabilityRUSTSEC-2022-0075 · 2022-11-10Bug in pooling instance allocator
- Vulnerability HighRUSTSEC-2022-0076 · 2022-11-10Bug in Wasmtime implementation of pooling instance allocator
- VulnerabilityRUSTSEC-2022-0095 · 2022-06-27Miscompilation of `i8x16.swizzle` and `select` with v128 inputs
- VulnerabilityRUSTSEC-2022-0096 · 2022-02-17Invalid drop of VMExternRef from partially-initialized instances in the pooling instance allocator
- Vulnerability HighRUSTSEC-2022-0098 · 2022-11-05Data leakage between instances in the pooling allocator
- VulnerabilityRUSTSEC-2022-0099 · 2022-03-28 Use after free with `externref`s and epoch interruption in Wasmtime
Up next
Same cratewasmtime: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?