CVE-2026-34943 — Vulnerability in wasmtime — CVE Details
Wasmtime has a possible panic when lifting `flags` component value
Summary
Advisory Timeline
- First published April 9, 2026 (186 days ago).
- Last revised September 10, 2026 — 153 days after initial publication.
Remediation
Upgrade to the fixed version using your package manager.
cargo update -p wasmtime --precise 36.0.7
cargo update -p wasmtime --precise 42.0.2
cargo update -p wasmtime --precise 43.0.1
cargo update -p wasmtime --precise 24.0.7
After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.
Affected Packages (4)
Affects 1 ecosystem: crates.io (1).
Vulnerability Classification
Common Weakness Enumeration (CWE) identifiers for this vulnerability type.
- CWE-248
CVSS Score Breakdown
What the CVSS (Common Vulnerability Scoring System) 7.5 score means for each attack dimension.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
Frequently Asked Questions
- What is CVE-2026-34943?
- Wasmtime has a possible panic when lifting `flags` component value This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 7.5/10).
- How do I check if my project is affected by CVE-2026-34943?
- CVE-2026-34943 affects wasmtime. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-34943 and 200,000+ other known vulnerabilities.
Severity & Exploitability
High exploitability or significant impact. Prioritize remediation within days.
Also Known As
Related CVEs
- RUSTSEC-2026-0327CRITICAL
Wasmtime component async-lifted callback result count is unvalidated, causing a native stack buffer overflow
- CVE-2023-26489CRITICAL
wasmtime vulnerable to guest-controlled out-of-bounds read/write on x86_64
- CVE-2022-24791HIGH
Use after free in Wasmtime
- CVE-2026-27572MEDIUM
Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance
- CVE-2026-35195MEDIUM
Wasmtime has out-of-bounds write or crash when transcoding component model strings
- CVE-2026-27204MEDIUM
Wasmtime WASI implementations are vulnerable to guest-controlled resource exhaustion
- CVE-2026-35186MEDIUM
Wasmtime has improperly masked return value from `table.grow` with Winch compiler backend
- CVE-2024-51745LOW
Wasmtime doesn't fully sandbox all the Windows device filenames
Check if you're affected
Scan your dependencies to see if this vulnerability affects your projects.
Scan Your Dependencies