CVE-2025-43853: iwasm vulnerable to filesystem sandbox escape with symlink when using uvwasi feature
bytecodealliance · wasm-micro-runtime
Affected: bytecodealliance wasm-micro-runtime · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 22% of scored CVEs
DescriptionCVE.org
The WebAssembly Micro Runtime's (WAMR) iwasm package is the executable binary built with WAMR VMcore which supports WebAssembly System Interface (WASI) and command line interface. Anyone running WAMR up to and including version 2.2.0 or WAMR built with libc-uvwasi on Windows is affected by a symlink following vulnerability. On WAMR running in Windows, creating a symlink pointing outside of the preopened directory and subsequently opening it with create flag will create a file on host outside of the sandbox. If the symlink points to an existing host file, it's also possible to open it and read its content. Version 2.3.0 fixes the issue.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- bytecodealliance · wasm-micro-runtime< 2.3.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- bytecodealliance
- Published
- May 2025
CoverageNo articles yet
No CyberSIXT article names CVE-2025-43853 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.