wasmtime vulnerabilities — 10 matching vulnerabilities

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed — no installation and no source-code access required.

Scan your app free →

Severity	Vulnerability	Package	Ecosystem	Disclosed	Fixed version
Medium	Critical Memory Access Vulnerability in Wasmtime: UNKNOWN READ Issue	`wasmtime`	OSS-Fuzz	21 Apr 2026	eb7a3f61290ac9e82fe7d760fb569bb3f3fc657a
High	Critical Memory Write Vulnerability in Wasmtime Package	`wasmtime`	OSS-Fuzz	23 Feb 2026	c07c94d2f69265cb0661e446a4daee0de5e69cf1
Unrated	Segmentation Fault Vulnerability in Wasmtime: Cranelift Function Runner Crash	`wasmtime`	OSS-Fuzz	19 Oct 2024	b62651fb5203cec51a45dba6a85983de3c45d942
High	UNKNOWN WRITE vulnerability in wasmtime	`wasmtime`	OSS-Fuzz	15 Nov 2022	3535acbf3be032ef1ba0b469b8ab92538a8a18a6
High	UNKNOWN WRITE vulnerability in wasmtime	`wasmtime`	OSS-Fuzz	08 Nov 2022	dece901d1694bd5f148b67afc9a512e4cc344591
Unrated	Segv on unknown address in wasmtime_runtime::traphandlers::catch_traps::call_closure::hec711b3339636b04	`wasmtime`	OSS-Fuzz	26 Aug 2022	dde2c5a3b6ee6caa1d597da0885613d2ce6a406a
Unrated	Segv on unknown address in cranelift_filetests::function_runner::CompiledFunction::call::ha6b9162cd2eNUMBER	`wasmtime`	OSS-Fuzz	24 Aug 2022	573ae0c60bb20e010d74ba7fd2e7e59247f3385d
High	Heap-use-after-free vulnerability in wasmtime	`wasmtime`	OSS-Fuzz	19 Jul 2022	No fix published
High	Heap-use-after-free in .tmpoLlNv4 in wasmtime	`wasmtime`	OSS-Fuzz	19 Jul 2022	2154c63de94e0372bca5a596c3eaf90147c922d1
High	Heap-use-after-free vulnerability in wasmtime	`wasmtime`	OSS-Fuzz	19 Jul 2022	2154c63de94e0372bca5a596c3eaf90147c922d1

Subscribe to Vulert on Telegram

Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.

Join the channel →

Questions

Searching the database

How do I search for a CVE or a package?

Type a CVE id, package name, ecosystem or keyword into the search field. Results include the severity, the affected package, the ecosystem, the disclosure date and the fixed version.

Can I filter by severity or by whether a fix exists?

Yes. The filters on the left narrow the list to critical, high, medium or low vulnerabilities, to a single ecosystem, and to vulnerabilities that have a fix available or none yet.

What does "No fix published" mean?

No patched version has been released for that vulnerability yet. The vulnerability page still shows the affected range and any workaround that can reduce exposure in the meantime.