bytecodealliance vulnerabilities
Every vulnerability this feed holds for bytecodealliance, merged from five public registers and ordered by what warrants attention first — exploited in the wild, then CVSS, then recency.
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…
- 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…
- 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…
- 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…
- 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…
- 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…
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 bytecodealliance is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other vendors tracked here
Microsoft Red Hat Google n/a Apache Software Foundation Linux MediaTek, Inc. Apple FreeRDP Eclipse Foundation Gitea WAVLINK Dell vim vercel jpadilla Huawei Unknown Oracle Corporation py-pdf AM System WSO2 MONGODB Elastic