wasmtime vulnerabilities and CVEs

Known vulnerabilities affecting wasmtime, with exploit availability attached to each one, so you can tell a flaw someone has written code for from one nobody has.

6 vulnerabilities tracked.

6.9 Wasmtime 46.0.0 before 48.0.7 and 49.0.0 before 49.0.4 contains a response splitting vulnerability in wasi-http p3 that allows guests to… CVE-2026-121439 3 Nov 2026
6.3 Wasmtime 46.0.0 before 48.0.7 and 49.0.0 before 49.0.4 fails to check forwarded trailers against the WasiHttpHooks::isforbiddenheader hook… CVE-2026-121440 3 Nov 2026
6.3 Wasmtime before 36.0.19, 37.0.0 before 48.0.7, and 49.0.0 before 49.0.4 contains a request smuggling vulnerability in wasi-http that allows… CVE-2026-121441 3 Nov 2026
5.9 Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains a denial of service vulnerability that allows malicious components to panic… CVE-2026-119140 29 Oct 2026
5.9 Wasmtime 42.0.0 before 48.0.6 and 49.0.0 before 49.0.3 contains insufficient checks in Store when mixing async-style and sync-style… CVE-2026-119136 29 Oct 2026
5.9 Wasmtime from 49.0.0 before 49.0.3 contains a denial-of-service vulnerability that allows a WebAssembly guest to trigger a host panic by… CVE-2026-119132 29 Oct 2026

What this covers

This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that wasmtime is free of vulnerabilities.

Query this from an agent over MCP · Check a lockfile by version

wasmtime vulnerabilities and CVEs

What this covers

Other products tracked here