CVE-2021-39216

What it is

Wasmtime is an open source runtime for WebAssembly & WASI. In Wasmtime from version 0.19.0 and before version 0.30.0 there was a use-after-free bug when passing `externref`s from the host to guest Wasm content. To trigger the bug, you have to explicitly pass multiple `externref`s from the host to a Wasm instance at the same time, either by passing multiple `externref`s as arguments from host code to a Wasm function, or returning multiple `externref`s to Wasm from a multi-value return function defined in the host. If you do not have host code that matches one of these shapes, then you are not impacted. If Wasmtime's `VMExternRefActivationsTable` became filled to capacity after passing the first `externref` in, then passing in the second `externref` could trigger a garbage collection. However the first `externref` is not rooted until we pass control to Wasm, and therefore could be reclaimed by the collector if nothing else was holding a reference to it or otherwise keeping it alive. Then, when control was passed to Wasm after the garbage collection, Wasm could use the first `externref`, which at this point has already been freed. We have reason to believe that the effective impact of this bug is relatively small because usage of `externref` is currently quite rare. The bug has been fixed, and users should upgrade to Wasmtime 0.30.0. If you cannot upgrade Wasmtime yet, you can avoid the bug by disabling reference types support in Wasmtime by passing `false` to `wasmtime::Config::wasm_reference_types`.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. High risk of data tampering, service disruption.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2021-09-17 20:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 04:03 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 6.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2021-09-17 20:15 UTC

Last modified

2026-06-17 04:03 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-416 · Use after free

Record status

Modified

Affected

• Bytecodealliance Wasmtime < 0.30.0
• Fedoraproject Fedora 34
• Fedoraproject Fedora 35

Attack profile CVSS 3.1 · 6.3

Attack vector

Local

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2021-39216.md and follow it. Check whether this project is affected by CVE-2021-39216. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge