Advisory Database
  • Advisories
  • Dependency Scanning
  1. cargo
  2. ›
  3. wasmtime
  4. ›
  5. CVE-2026-34983

CVE-2026-34983: Wasmtime has use-after-free bug after cloning `wasmtime::Linker`

April 9, 2026

In version 43.0.0 of the wasmtime crate, cloning a wasmtime::Linker is unsound and can result in use-after-free bugs.

This bug is not controllable by guest Wasm programs. It can only be triggered by a specific sequence of embedder API calls made by the host.

The typical symptom of this use-after-free bug is a segfault. It does not enable heap corruption or data leakage.

If you are using the wasmtime CLI, rather than the embedding API, you are not affected. If you are using the embedding API but are not calling wasmtime::Linker’s Clone implementation, you are not affected.

Specifically, the following steps must occur to trigger the bug:

  • Clone a wasmtime::Linker
  • Drop the original linker instance
  • Use the new, cloned linker instance, resulting in a use-after-free

References

  • github.com/advisories/GHSA-hfr4-7c6c-48w2
  • github.com/bytecodealliance/wasmtime
  • github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hfr4-7c6c-48w2
  • nvd.nist.gov/vuln/detail/CVE-2026-34983

Code Behaviors & Features

Detect and mitigate CVE-2026-34983 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions starting from 43.0.0 before 43.0.1, version 43.0.0

Fixed versions

  • 43.0.1

Solution

Upgrade to version 43.0.1 or above.

Impact 3.5 LOW

CVSS:3.1/AV:P/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L

Learn more about CVSS

Weakness

  • CWE-416: Use After Free

Source file

cargo/wasmtime/CVE-2026-34983.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Fri, 10 Apr 2026 12:18:03 +0000.