Is wasmtime affected by CVE-2026-34983?

crates.io wasmtime is affected in >=43.0.0 <43.0.1.

Is CVE-2026-34983 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.1%.

low

CVE-2026-34983

Q: Is CVE-2026-34983 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.1%.

crates.io · wasmtime • PyPI · wasmtime

Summary

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

Severity: low
EPSS: 0.1% (p2)
Also known as: GHSA-hfr4-7c6c-48w2, PYSEC-2026-151, RUSTSEC-2026-0090
Published: 2026-04-09

References

Related advisories

CVE-2026-34987 — critical · crates.io/wasmtime
CVE-2026-34971 — critical · crates.io/wasmtime
CVE-2023-26489 — critical · crates.io/wasmtime
CVE-2022-39393 — high · crates.io/wasmtime
CVE-2022-24791 — high · crates.io/wasmtime
CVE-2026-44216 — medium · crates.io/wasmtime
CVE-2026-35186 — medium · crates.io/wasmtime
CVE-2026-35195 — medium · crates.io/wasmtime

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.