← Back
CVE-2026-47261
high
CVSS 7.5
Vulnerability in wasmtime-wasi (CVE-2026-47261)
Summary
vulnerability in wasmtime-wasi (CVE-2026-47261). Data can be tampered with by attackers. Exploitable via ``path_open``. Mitigation: upgrade to `24.0.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-47261** has been found in wasmtime-wasi.
Attackers can target a specific entry point like ``path_open`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade wasmtime-wasi to **24.0.9** or later.
If unsure, ask your IT team or search "wasmtime-wasi CVE-2026-47261" on the vendor's site.
CVE-2026-47261 (wasmtime-wasi) — CWE-284 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `path_open` / `FilePerms` / `ERRNO_PERM` / `WasiCtxBuilder`
Patched: `24.0.9` — apply immediately
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-284) exists in wasmtime-wasi. Attackers reach the vulnerable code path via ``path_open`` without authentication.
📍 Affected scope
wasmtime-wasi — . Attack surface: `path_open` / `FilePerms` / `ERRNO_PERM` / `WasiCtxBuilder`.
🔥 Severity
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **24.0.9**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade wasmtime-wasi to 24.0.9ステージング環境で 24.0.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
crates.io
wasmtime-wasi
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"24.0.9"}]}]
rust
wasmtime-wasi
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"24.0.9"}]}]
References
- package https://crates.io/crates/wasmtime-wasi
- package https://github.com/bytecodealliance/wasmtime
- web https://rustsec.org/advisories/RUSTSEC-2026-0149.html
- web https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-2r75-cxrj-cmph
- web https://github.com/bytecodealliance/wasmtime/releases/tag/v24.0.9
- web https://github.com/bytecodealliance/wasmtime/releases/tag/v36.0.10
- web https://github.com/bytecodealliance/wasmtime/releases/tag/v44.0.2
- web https://github.com/bytecodealliance/wasmtime/releases/tag/v45.0.0
- web https://github.com/advisories/GHSA-2r75-cxrj-cmph
- web https://nvd.nist.gov/vuln/detail/CVE-2026-47261