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.
CVE-2026-58494
This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(medium)
- EPSS
- 2.1%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 10, 2026
Advisory Details (9)
Auto-updated Jul 8, 2026Release v46.0.1 (bytecodealliance/wasmtime)
Patch available: bytecodealliance/wasmtime v46.0.1
https://github.com/bytecodealliance/wasmtime/releases/tag/v46.0.1Release v45.0.3 (bytecodealliance/wasmtime)
Patch available: bytecodealliance/wasmtime v45.0.3
https://github.com/bytecodealliance/wasmtime/releases/tag/v45.0.3Release v36.0.12 (bytecodealliance/wasmtime)
Patch available: bytecodealliance/wasmtime v36.0.12
https://github.com/bytecodealliance/wasmtime/releases/tag/v36.0.12Release v24.0.11 (bytecodealliance/wasmtime)
Patch available: bytecodealliance/wasmtime v24.0.11
https://github.com/bytecodealliance/wasmtime/releases/tag/v24.0.11commit d3ceb56ec35f (bytecodealliance/wasmtime)
Fix landed in bytecodealliance/wasmtime commit d3ceb56ec35f — awaiting tagged release
https://github.com/bytecodealliance/wasmtime/commit/d3ceb56ec35f39e02496eeb4e2d9c7f4fb964d9ecommit 8a250aac0962 (bytecodealliance/wasmtime)
Fix landed in bytecodealliance/wasmtime commit 8a250aac0962 — awaiting tagged release
https://github.com/bytecodealliance/wasmtime/commit/8a250aac0962ca1364b5f16525720e9d0b39edcdcommit 7db94cdcf0c7 (bytecodealliance/wasmtime)
Fix landed in bytecodealliance/wasmtime commit 7db94cdcf0c7 — awaiting tagged release
https://github.com/bytecodealliance/wasmtime/commit/7db94cdcf0c79cb3dfde884b534b653f2dd83367commit 5ddfd5f1ef28 (bytecodealliance/wasmtime)
Fix landed in bytecodealliance/wasmtime commit 5ddfd5f1ef28 — awaiting tagged release
https://github.com/bytecodealliance/wasmtime/commit/5ddfd5f1ef28f2041fa07d237ad0336e167b0e0cWASI hard links and renames bypass wasmtime-wasi's FilePerms for destination · Advisory · bytecodealliance/wasmtime · GitHub
https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-4ch3-9j33-3pmjAffected Packages
(1 across 1 ecosystem)
crates.io(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| wasmtime-wasi | — | 46.0.1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 01:56 UTCEG score recompute
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 00:13 UTCEG score recompute
- 2026-07-09 22:26 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 20:44 UTCEG score recompute
- 2026-07-08 20:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863 · CWE-281
Frequently asked(5)
What is CVE-2026-58494?
When was CVE-2026-58494 disclosed?
Is CVE-2026-58494 actively exploited?
What is the CVSS score of CVE-2026-58494?
How do I remediate CVE-2026-58494?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58494
Is Your Infrastructure Affected by CVE-2026-58494?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.