Analysis
Analysis and contextual insights are available on OpenCVE Cloud.
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bytecodealliance | wasmtime | unaffected |
|
No data.
No data.
No data available yet.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 23 Oct 2026 00:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | 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 | |
| First Time appeared |
Bytecodealliance
Bytecodealliance wasmtime |
|
| Weaknesses | CWE-400 | |
| CPEs | cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Bytecodealliance
Bytecodealliance wasmtime |
|
| References |
| |
| Metrics |
cvssV3_1
|
MITRE
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-10-22T19:13:54.430Z
Reserved: 2026-10-22T11:25:27.611Z
Link: CVE-2026-115388
Vulnrichment
No data.
NVD
Status : Deferred
Published: 2026-10-22T19:17:46.173
Modified: 2026-10-22T19:17:46.290
Link: CVE-2026-115388
Redhat
No data.
OpenCVE Enrichment
No data.
-
CWE-400
Uncontrolled Resource Consumption