Embedding-process crash via dangling cloned string keys
Published Apr 9, 2026 · Updated Apr 9, 2026
Use-after-free in Wasmtime 43.0.0 allows local users controlling host API calls to crash an embedding process through Linker cloning. StringPool::try_clone copies map keys that reference the original pool's string storage, leaving dangling keys after the original Linker is dropped. Guest Wasm and the CLI cannot reach the flaw; the host must clone a Linker, drop the original, and use the clone, and the reported consequence is a segfault without heap corruption or data leakage.
Summary
What happened
Use-after-free in Wasmtime 43.0.0 allows local users controlling host API calls to crash an embedding process through Linker cloning. StringPool::try_clone copies map keys that reference the original pool's string storage, leaving dangling keys after the original Linker is dropped. Guest Wasm and the CLI cannot reach the flaw; the host must clone a Linker, drop the original, and use the clone, and the reported consequence is a segfault without heap corruption or data leakage.
The record
- CVE
- CVE-2026-34983
- Published
- Apr 9, 2026
- Updated
- Apr 9, 2026
- Vendor
- Bytecode Alliance
- Product
- Wasmtime
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 9, 2026CVE publishedPublication date reported by the CVE source.
- Apr 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 43.0.0, < 43.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Linker clone-drop regression reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo