CVE-2026-115388 json
Wasmtime before 36.0.16, 37.0.0 before 48.0.3, and 49.0.0 before 49.0.1 Memory Exhaustion DoS via wasmtime-wasi-http Outgoing Body Write
published last mo. modified 11d ago also EUVD-2026-108318 , GHSA-c9gc-w9vx-w86p , RUSTSEC-2026-0313
- cvss
- 6.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
wasmtime-wasi-http in Wasmtime before 36.0.16, 37.0.0 before 48.0.3, and 49.0.0 before 49.0.1 does not enforce the wasi:io/streams check-write allowance for WASIp2 outgoing HTTP bodies, so oversized writes succeed instead of trapping. A malicious guest can pass large buffers to write on outgoing-body resources, holding host allocations for the store's lifetime and exhausting host memory.
Patch / fix
- crates.io wasmtime-wasi-http 36.0.16, 48.0.3, 49.0.1
- bytecodealliance wasmtime 36.0.16, 48.0.3, 49.0.1
- github.com/bytecodealliance/wasmtime#14408 pull request
Is CVE-2026-115388 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 11d ago
Exploit prediction
0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| OSV | 3.1 | 6.2 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | wasmtime-wasi-http | >=0.0.0-0, <36.0.16 >=37.0.0, <48.0.3 >=49.0.0, <49.0.1 |
36.0.16 48.0.3 49.0.1 |
Affected products
- bytecodealliance wasmtime
Classification
- Weakness
-
- CWE-400 Uncontrolled Resource Consumption
References
-
github.com
/bytecodealliance/wasmtime/pull/14408
web
-
github.com
/bytecodealliance/wasmtime/security/advisories/GHSA-c9gc-w9vx-w86p
vendor-advisory
-
vulncheck.com
/advisories/wasmtime-before-36.0.16-37.0.0-before-48.0.3-and-49.0.0-before-49.0.1-memory-exhaustion-dos-via-wa
third-party-advisory
-
crates.io
/crates/wasmtime-wasi-http
package
-
rustsec.org
/advisories/RUSTSEC-2026-0313.html
advisory
Sources
- CVE List CVE-2026-115388
- NVD CVE-2026-115388
- OSV RUSTSEC-2026-0313
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.