Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Medium severity, with a CVSS score of 4, published 2 October 2026.

Which products and versions are affected?

Bytecode Alliance Wasmtime-Wasi <36.0.17, 37.0.0-48.0.3, 49.0.0-49.0.1; wasmtime-wasi (crates.io) SEMVER:introduced=0.0.0-0,fixed=36.0.17,introduced=37.0.0,fixed=48.0.4,introduced=49.0.0,fixed=49.0.2.

Is there a fix for This vulnerability?

Yes. wasmtime-wasi (crates.io): upgrade to 49.0.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network, in a software library.

Check whether you run Bytecode Alliance Wasmtime-Wasi or wasmtime-wasi (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Wasmtime wasmtime-wasi fd_readdir information disclosure

Q: Is there a fix for This vulnerability?

Yes. wasmtime-wasi (crates.io): upgrade to 49.0.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

It is attacked over the network, in a software library.

Q: Am I affected?

Check whether you run Bytecode Alliance Wasmtime-Wasi or wasmtime-wasi (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Severity: medium · CVSS 4 · Published 2026-10-02

Wasmtime is a WebAssembly runtime that executes untrusted code in sandboxed environments. A flaw in the file directory reading function copies uninitialized memory from the host system into the WebAssembly guest, potentially exposing sensitive data from the host to untrusted guest code. This requires an attacker to have WASM code execution in the runtime and user interaction to trigger the vulnerable code path.

Technologies: Bytecode Alliance Wasmtime-Wasi, wasmtime-wasi (crates.io). Vendors: Bytecode Alliance, crates.io.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Medium severity, with a CVSS score of 4, published 2 October 2026.
Which products and versions are affected?: Bytecode Alliance Wasmtime-Wasi <36.0.17, 37.0.0-48.0.3, 49.0.0-49.0.1; wasmtime-wasi (crates.io) SEMVER:introduced=0.0.0-0,fixed=36.0.17,introduced=37.0.0,fixed=48.0.4,introduced=49.0.0,fixed=49.0.2.
Is there a fix for This vulnerability?: Yes. wasmtime-wasi (crates.io): upgrade to 49.0.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a software library.
Am I affected?: Check whether you run Bytecode Alliance Wasmtime-Wasi or wasmtime-wasi (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

wasmtime-wasi (crates.io): upgrade to 49.0.2 or later
```
cargo update -p wasmtime-wasi
```

Technical details

The fd_readdir function in wasmtime-wasi fails to zero struct padding before copying directory entry data to guest memory, leaking uninitialized host memory contents. The vulnerability requires network access, low privileges, and passive user interaction to exploit. An attacker gains access to host memory contents that may contain sensitive information.

Affected products

Bytecode Alliance wasmtime-wasi <36.0.17, 37.0.0-48.0.3, 49.0.0-49.0.1

Identifiers

GHSA-96f6-r43r-8c24
RUSTSEC-2026-0323

Timeline

2026-10-02: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.