GHSA-f8mm-ggr3-89wh json
wasmtime-wasi-http: Empty Body Writes can result in Unbound Heap Usage with HTTP/2
published 4d ago modified yesterday also RUSTSEC-2026-0571
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-f8mm-ggr3-89wh For more information see the GitHub-hosted security advisory.
Patch / fix
- crates.io wasmtime 36.0.21, 48.0.9, 49.0.6, 50.0.2
- github.com/bytecodealliance/wasmtime#15315 pull request
Is GHSA-f8mm-ggr3-89wh in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | wasmtime | >=0.0.0-0, <36.0.21 >=37.0.0, <48.0.9 >=49.0.0, <49.0.6 >=50.0.0, <50.0.2 |
36.0.21 48.0.9 49.0.6 50.0.2 |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.