Advisory

GHSA-m758-wjhj-p3jq

Also known as: CVE-2026-34943, RUSTSEC-2026-0085

Summary

Wasmtime has a possible panic when lifting flags component value

Details

Impact

Wasmtime contains a possible panic which can happen when a flags-typed component model value is lifted with the Val type. If bits are set outside of the set of flags the component model specifies that these bits should be ignored but Wasmtime will panic when this value is lifted. This panic only affects wasmtime's implementation of lifting into Val, not when using the flags! macro. This additionally only affects flags-typed values which are part of a WIT interface.

This has the risk of being a guest-controlled panic within the host which Wasmtime considers a DoS vector.

Patches

Wasmtime 24.0.7, 36.0.7, 42.0.2, and 43.0.1 have been issued to fix this bug. Users are recommended to update to these patched versions of Wasmtime.

Workarounds

There is no workaround for this bug if a host meets the criteria to be affected. To be affected a host must be using wasmtime::component::Val and possibly work with a flags type in the component model.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-04-09 20:22 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

wasmtime

crates.io · All systems

Affected

  • introduced 0, fixed 24.0.7 (semver)

Fixed versions

24.0.7

Fix

  • Fixed version 24.0.7
    cargo update -p wasmtime --precise 24.0.7

wasmtime

crates.io · All systems

Affected

  • introduced 25.0.0, fixed 36.0.7 (semver)

Fixed versions

36.0.7

Fix

  • Fixed version 36.0.7
    cargo update -p wasmtime --precise 36.0.7

wasmtime

crates.io · All systems

Affected

  • introduced 37.0.0, fixed 42.0.2 (semver)

Fixed versions

42.0.2

Fix

  • Fixed version 42.0.2
    cargo update -p wasmtime --precise 42.0.2

wasmtime

crates.io · All systems

Affected

  • introduced 43.0.0, fixed 43.0.1 (semver)

Fixed versions

43.0.1

Fix

  • Fixed version 43.0.1
    cargo update -p wasmtime --precise 43.0.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences