Wasmtime memory exhaustion in component resource handles
bytecodealliance wasmtime
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| wasmtime crates.io |
|
|
Original description
Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 caps component-model resource handle tables only per component instance and does not charge handle allocations to any ResourceLimiter or StoreLimits. A malicious guest can repeatedly call resource.new and instantiate sub-components to exceed the per-instance cap many times over, causing unbounded host memory growth.
From the CVE record · VulnCheck
References
- github.com/bytecodealliance/wasmtime/security/advisories/GHSA-q554-3cjc-rx7p
- vulncheck.com/advisories/wasmtime-before-36.0.18-37.0.0-before-48.0.6-and-49.0.0-before-49.0.3-unbounded-memory-growth-via-component-model-resource-handles
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/119xxx/CVE-2026-119134.json
- nvd.nist.gov/vuln/detail/CVE-2026-119134
- crates.io/crates/wasmtime
- rustsec.org/advisories/RUSTSEC-2026-0363.html
- github.com/bytecodealliance/wasmtime/pull/14732