Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44216 high CVSS 7.5

Vulnerability in wasmtime (CVE-2026-44216)

Summary

Vulnerability in wasmtime (CVE-2026-44216). Risk of unauthorized operations or information disclosure. Exploitable via memory64. Mitigation: upgrade to 43.0.2 or later.

Original description

The description as published by the source.

Wasmtime is a runtime for WebAssembly. From 30.0.0 to 36.0.8, 43.0.2, and 44.0.1, Wasmtime's allocation logic for a WebAssembly table contained checked arithmetic which panicked on overflow. This overflow is possible to trigger, and thus panic, when a table with an extremely large size is allocated. This is possible with the WebAssembly memory64 proposal where tables can have sizes in the 64-bit range as opposed to the previous 32-bit range which would not overflow. The panic happens when attempting to create a very large table, such as when instantiating a WebAssembly module or component. This vulnerability is fixed in 36.0.8, 43.0.2, and 44.0.1.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-44216 has been found in wasmtime.
Attackers can target a specific entry point like memory64 over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade wasmtime to 43.0.2 or later.
If unsure, ask your IT team or search "wasmtime CVE-2026-44216" on the vendor's site.

CVE-2026-44216 (wasmtime) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: memory64
Patched: 43.0.2 — apply immediately
Workaround: Embeddings can switch to using the pooling allocator to work around this issue, or the memory64 WebAssembly proposal can be disabled.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-770) exists in wasmtime. Attackers reach the vulnerable code path via memory64 without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of wasmtime. Attack surface: memory64.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 43.0.2.

🛡️ Workaround

Workaround: Embeddings can switch to using the pooling allocator to work around this issue, or the memory64 WebAssembly proposal can be disabled.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'wasmtime' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'wasmtime' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で wasmtime を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Embeddings can switch to using the pooling allocator to work around this issue, or the `memory64` WebAssembly proposal can be disabled.

    パッチが適用されるまでの応急処置として、Embeddings can switch to using the pooling allocator to work around this issue, or the memory64 WebAssembly proposal can be disabled. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade wasmtime to 43.0.2

    ステージング環境で 43.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rust wasmtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"43.0.2"}]}]
crates.io wasmtime
[{"type":"SEMVER","events":[{"introduced":"30.0.0"},{"fixed":"36.0.8"},{"introduced":"37.0.0"},{"fixed":"43.0.2"},{"introduced":"44.0.0"},{"fixed":"44.0.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details