Vulnerability in rust-wasmtime (UBUNTU-CVE-2026-58494)
Summary
Vulnerability in rust-wasmtime (UBUNTU-CVE-2026-58494). Data can be tampered with by attackers.
Original description
The description as published by the source.
Wasmtime is a runtime for WebAssembly. Prior to 24.0.11, 36.0.12, 45.0.3, and 46.0.1, wasmtime-wasi hard-link creation and renaming check directory permissions but not matching FilePerms on source and destination preopens, allowing a WASI guest with a read-only source file capability to overwrite host files exposed as FilePerms::READ through wasip1, wasip2, or wasip3 filesystem interfaces. This issue is fixed in versions 24.0.11, 36.0.12, 45.0.3, and 46.0.1.
Source: OSV.dev (Open Source Vulnerabilities) OSV
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 UBUNTU-CVE-2026-58494 has been found in rust-wasmtime.
Data can be tampered with by attackers.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "rust-wasmtime UBUNTU-CVE-2026-58494" on the vendor's site.
UBUNTU-CVE-2026-58494 (rust-wasmtime)
Attack vector: local / no user interaction
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.
A vulnerability (unclassified) exists in rust-wasmtime.
Check the vendor advisory for the affected versions of rust-wasmtime.
Severity: ?. Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'rust-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
-
1Identify exposure identify
grep -r 'rust-wasmtime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
rust-wasmtimeを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- report ubuntu.com
- report cve.org
- report github.com
- report github.com
- report github.com
- report github.com
- report github.com
- report github.com
- report github.com
- report github.com
- report github.com