CVE-2026-115388 Details
Description
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.
A denial-of-service vulnerability has been identified in the wasmtime-wasi-http component of Wasmtime. This issue is present in versions prior to 36.0.16, 37.0.0 prior to 48.0.3, and 49.0.0 prior to 49.0.1. The vulnerability arises because the outgoing HTTP body write operation does not properly enforce the write allowance specified by the wasi:io/streams.check-write function. As a result, malicious guests can send large buffers through outgoing-body resources, which are then held in memory for the duration of the guest's store. This behavior leads to excessive memory consumption on the host.
Users can upgrade to Wasmtime versions 36.0.16, 48.0.3, or 49.0.1 to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Oct 22, 2026CISA-ADP
Assessed Oct 29, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-400 | Uncontrolled Resource Consumption | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| bytecodealliance wasmtime-wasi-http | < 36.0.16 (semver) >= 37.0.0, < 48.0.3 (semver) >= 49.0.0, < 49.0.1 (semver) |
CPE
Remediation
| |
| bytecodealliance wasmtime | All versions |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 29, 2026 | CVE Modified | CISA-ADP |
| Oct 22, 2026 | New CVE Received | [email protected] |
Volerion