CVE-2026-119134

Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 Unbounded Memory Growth via Component-Model Resource Handles

Published Oct 29, 2026 CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
Description
Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 caps component-model resource handle tables only per component instance and does not charge handle allocations to any ResourceLimiter or StoreLimits. A malicious guest can repeatedly call resource.new and instantiate sub-components to exceed the per-instance cap many times over, causing unbounded host memory growth.

Analysis

AI-generated

Technical impact

Wasmtime prior to the specified versions fails to limit allocation of component-model resource handles per instance and does not apply any ResourceLimiter or StoreLimits to these allocations, allowing a malicious guest to repeatedly create new resources and spawn sub-components until the host machine’s memory is exhausted. The impact is unbounded host memory growth, which can exhaust system resources and cause a denial of service. The weakness corresponds to CWEs that involve resource exhaustion.

Affected Systems

The vulnerability affects Wasmtime releases before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3. The affected product is the Wasmtime WebAssembly runtime from Bytecode Alliance.

Risk and Exploitability

The CVSS score of 6.9 indicates a moderate severity. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, suggesting no widely publicized exploit yet. However, any process that runs untrusted Wasm components could potentially trigger the unbounded growth, so the attack vector is likely through execution of malicious guest code. The risk increases in environments where Wasmtime is exposed to untrusted inputs or where system memory limits are not enforced externally.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Wasmtime to a version that includes the fix (36.0.18, 48.0.6, or 49.0.3 and later).
  • If an immediate upgrade is not possible, verify whether host resource limits or a ResourceLimiter can be applied to bound component instance handle allocations; apply such limits if available.
  • Implement OS‑level memory constraints such as cgroups or other container resource limits to cap the memory usage of Wasmtime processes, mitigating the effect of any unbounded growth.

Generated by OpenCVE AI on October 29, 2026 at 17:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 caps component-model resource handle tables only per component instance and does not charge handle allocations to any ResourceLimiter or StoreLimits. A malicious guest can repeatedly call resource.new and instantiate sub-components to exceed the per-instance cap many times over, causing unbounded host memory growth.
Title Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 Unbounded Memory Growth via Component-Model Resource Handles
First Time appeared Bytecodealliance
Bytecodealliance wasmtime
Weaknesses CWE-770
CPEs cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:*:*:*
Vendors & Products Bytecodealliance
Bytecodealliance wasmtime
References
Metrics cvssV3_1

{'score': 6.2, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

cvssV4_0

{'score': 6.9, 'vector': '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'}

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 29, 2026, 8:14 PM
Reserved
Oct 29, 2026, 2:26 PM
Status
Deferred
Published
Oct 29, 2026, 4:18 PM
Modified
Oct 29, 2026, 9:17 PM
Severity
Moderate
Public date
Oct 29, 2026, 3:58 PM