Is wasmtime affected by CVE-2021-39216?

crates.io wasmtime is affected in <0.30.0.

Is CVE-2021-39216 being exploited?

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

medium

CVE-2021-39216

Q: Is CVE-2021-39216 being exploited?

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

crates.io · wasmtime

Summary

Wrong type for `Linker`-define functions when used across two `Engine`s

Severity: medium
EPSS: 0.3% (p21)
Also known as: CVE-2021-39218, CVE-2021-39219, GHSA-4873-36h9-wv49, GHSA-q879-9g95-56mx, GHSA-v4cp-h94r-m7xf, PYSEC-2021-320, PYSEC-2021-321, PYSEC-2021-322, RUSTSEC-2021-0110
Published: 2021-09-20

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.