← Back
CVE-2026-54786
medium
CVSS 5.0
Vulnerability in wasmtime-wasi (CVE-2026-54786)
Summary
vulnerability in wasmtime-wasi (CVE-2026-54786). Risk of unauthorized operations or information disclosure. Exploitable via ``fd_renumber``. Mitigation: upgrade to `44.0.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54786** has been found in wasmtime-wasi.
Attackers can target a specific entry point like ``fd_renumber`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/10.
What to do: upgrade wasmtime-wasi to **44.0.3** or later.
If unsure, ask your IT team or search "wasmtime-wasi CVE-2026-54786" on the vendor's site.
CVE-2026-54786 (wasmtime-wasi) — CWE-400 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `fd_renumber` / `Store`
Patched: `44.0.3` — apply immediately
Workaround: There are no workarounds for this issue and hosts are recommended to update.
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-400) exists in wasmtime-wasi. Attackers reach the vulnerable code path via ``fd_renumber`` without authentication.
📍 Affected scope
wasmtime-wasi — . Attack surface: `fd_renumber` / `Store`.
🔥 Severity
Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **44.0.3**.
🛡️ Workaround
Workaround: There are no workarounds for this issue and hosts are recommended to update.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'wasmtime-wasi' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wasmtime-wasi' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `wasmtime-wasi` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
There are no workarounds for this issue and hosts are recommended to update.パッチが適用されるまでの応急処置として、There are no workarounds for this issue and hosts are recommended to update. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade wasmtime-wasi to 44.0.3ステージング環境で 44.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
wasmtime-wasi
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"44.0.3"}]}]
References
- web https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-3p27-qvp9-27qf
- web https://nvd.nist.gov/vuln/detail/CVE-2026-54786
- web https://github.com/bytecodealliance/wasmtime/pull/13650
- web https://github.com/bytecodealliance/wasmtime/commit/100bfe27253d2ce5154ddddf66d06e30f3fa6824
- web https://github.com/bytecodealliance/wasmtime/commit/36b305d827149ac0336ddcbc0a378c303339d195
- web https://github.com/bytecodealliance/wasmtime/commit/72493b11ed5df382c92a9dfb8b6bc064e471f1cd
- web https://github.com/bytecodealliance/wasmtime/commit/e9fbe974c9698edef117323d981e13caf2097c13
- web https://github.com/bytecodealliance/wasmtime/commit/f069f125cb77a4a3dced19a77d73790610678622
- web https://github.com/bytecodealliance/wasmtime/releases/tag/v24.0.10
- web https://github.com/bytecodealliance/wasmtime/releases/tag/v36.0.11
- web https://github.com/bytecodealliance/wasmtime/releases/tag/v44.0.3
- web https://github.com/bytecodealliance/wasmtime/releases/tag/v45.0.2
- web https://rustsec.org/advisories/RUSTSEC-2026-0182.html
- web https://github.com/advisories/GHSA-3p27-qvp9-27qf