cve.bz

CVE-2026-115388 bytecodealliance wasmtime: Uncontrolled Resource Consumption

6.9 mediumEPSS 0.1%Fix available

Medium (6.9) in bytecodealliance wasmtime. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in wasmtime-wasi-http 36.0.16, 48.0.3, 49.0.1.

On this page
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.

Severity

CVSS 4.0

6.9 medium
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

CVSS 3.1

6.2 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • wasmtime-wasi-http (crates.io): fixed in 36.0.16, 48.0.3, 49.0.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-115388 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115388?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115388?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-115388 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
bytecodealliance wasmtimebefore 36.0.16
bytecodealliance wasmtimefrom 37.0.0 before 48.0.3
bytecodealliance wasmtimefrom 49.0.0 before 49.0.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
RUSTSEC-2026-0313crates.iowasmtime-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

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu24.04:LTS, 26.04:LTS, 26.10rust-wasmtimeno fix listedUBUNTU-CVE-2026-115388

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON