CVE-2026-58494: bytecodealliance wasmtime · Improper Preservation of Permissions
Affects bytecodealliance wasmtimeSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium · fixed in 46.0.1 : update bytecodealliance wasmtime when convenient.
Data as of 20 Nov 2026, 17:35 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 46.0.1, 45.0.3, 36.0.12 +1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade wasmtime and bytecodealliance/wasmtime to 46.0.1, 45.0.3, 36.0.12 or 24.0.11.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| bytecodealliancewasmtime | Affected
| Fixed in
|
| bytecodealliancewasmtime | Affected
| Fixed in
|
| bytecodealliancewasmtime | Affected
| Fixed in
|
| bytecodealliancewasmtime | Affected
| Fixed in
|
GitHubbytecodealliance/wasmtimepkg:github/bytecodealliance/wasmtimeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Fixed versions 24.0.11, 36.0.12, 45.0.3, and 46.0.1 are available and should be applied to remediate this vulnerability. Since the vendor advisory indicates these versions fix the issue, upgrading to these or later versions is the recommended mitigation. Patch status is confirmed by the version fixes stated in the description. No additional vendor advisory content is provided.
Description
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.
References
- github.com/bytecodealliance/wasmtime/security/advisories/GHSA-4ch3-9j33-3pmj (opens in a new tab)
- github.com/bytecodealliance/wasmtime/commit/5ddfd5f1ef28f2041fa07d237ad0336e167b0e0c (opens in a new tab)
- github.com/bytecodealliance/wasmtime/commit/7db94cdcf0c79cb3dfde884b534b653f2dd83367 (opens in a new tab)
- github.com/bytecodealliance/wasmtime/commit/8a250aac0962ca1364b5f16525720e9d0b39edcd (opens in a new tab)
- github.com/bytecodealliance/wasmtime/commit/d3ceb56ec35f39e02496eeb4e2d9c7f4fb964d9e (opens in a new tab)
- github.com/bytecodealliance/wasmtime/releases/tag/v24.0.11 (opens in a new tab)
- github.com/bytecodealliance/wasmtime/releases/tag/v36.0.12 (opens in a new tab)
- github.com/bytecodealliance/wasmtime/releases/tag/v45.0.3 (opens in a new tab)
- github.com/bytecodealliance/wasmtime/releases/tag/v46.0.1 (opens in a new tab)