Skip to content

chore(deps): update rust crate wasmtime-wasi to v33.0.2 [security] - #165

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/crate-wasmtime-wasi-vulnerability
Open

chore(deps): update rust crate wasmtime-wasi to v33.0.2 [security]#165
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/crate-wasmtime-wasi-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Jul 19, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
wasmtime-wasi dev-dependencies patch =33.0.1=33.0.2

Wasmtime CLI is vulnerable to host panic through its fd_renumber function

CVE-2025-53901 / GHSA-fm79-3f68-h2fc

More information

Details

Summary

A bug in Wasmtime's implementation of the WASIp1 set of import functions can lead to a WebAssembly guest inducing a panic in the host (embedder).
The specific bug is triggered by calling path_open after calling fd_renumber with either:

  • two equal argument values
  • second argument being equal to a previously-closed file descriptor number value

The corrupt state introduced in fd_renumber will lead to the subsequent opening of a file descriptor to panic. This panic cannot introduce memory unsafety or allow WebAssembly to break outside of its sandbox, however. There is no possible heap corruption or memory unsafety from this panic.

This bug is in the implementation of Wasmtime's wasmtime-wasi crate which provides an implementation of WASIp1. The bug requires a specially crafted call to fd_renumber in addition to the ability to open a subsequent file descriptor. Opening a second file descriptor is only possible when a preopened directory was provided to the guest, and this is common amongst embeddings. A panic in the host is considered a denial-of-service vector for WebAssembly embedders and is thus a security issue in Wasmtime.

This bug does not affect WASIp2 and embedders using components.

Patches

In accordance with Wasmtime's release process patch releases are available as 24.0.4, 33.0.2, and 34.0.2. Users of other release of Wasmtime are recommended to move to a supported release of Wasmtime.

Workarounds

Embedders who are using components or are not providing guest access to create more file descriptors (e.g. via a preopened filesystem directory) are not affected by this issue. Otherwise there is no workaround at this time and affected embeddings are recommended to update to a patched version which will not cause a panic in the host.

Severity

  • CVSS Score: 3.5 / 10 (Low)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

bytecodealliance/wasmtime (wasmtime-wasi)

v33.0.2

Compare Source

33.0.2

Released 2025-07-18.

Fixed
  • Fix a panic in the host caused by preview1 guests using fd_renumber.
    CVE-2025-53901.

  • Fix a panic in the preview1 adapter caused by guests using fd_renumber.
    #​11277

33.0.1

Released 2025-06-24.

Fixed
  • Fix a panic with host-defined tables/globals and concrete reference
    types.
    #​11103

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled because a matching PR was automerged previously.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot force-pushed the renovate/crate-wasmtime-wasi-vulnerability branch 2 times, most recently from 9b0660c to 9ea2c3d Compare July 19, 2025 12:48
@renovate
renovate Bot force-pushed the renovate/crate-wasmtime-wasi-vulnerability branch from 9ea2c3d to 80b73e6 Compare August 10, 2025 14:27
@renovate
renovate Bot force-pushed the renovate/crate-wasmtime-wasi-vulnerability branch from 80b73e6 to da135a8 Compare September 25, 2025 15:15
@renovate
renovate Bot force-pushed the renovate/crate-wasmtime-wasi-vulnerability branch from da135a8 to a086b81 Compare December 10, 2025 14:43
@renovate renovate Bot changed the title chore(deps): update rust crate wasmtime-wasi to v33.0.2 [security] chore(deps): update rust crate wasmtime-wasi to v33.0.2 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/crate-wasmtime-wasi-vulnerability branch March 27, 2026 01:27
@renovate renovate Bot changed the title chore(deps): update rust crate wasmtime-wasi to v33.0.2 [security] - autoclosed chore(deps): update rust crate wasmtime-wasi to v33.0.2 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/crate-wasmtime-wasi-vulnerability branch 2 times, most recently from a086b81 to 4d6f969 Compare March 30, 2026 18:31
@renovate renovate Bot changed the title chore(deps): update rust crate wasmtime-wasi to v33.0.2 [security] chore(deps): update rust crate wasmtime-wasi to v33.0.2 [security] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title chore(deps): update rust crate wasmtime-wasi to v33.0.2 [security] - autoclosed chore(deps): update rust crate wasmtime-wasi to v33.0.2 [security] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/crate-wasmtime-wasi-vulnerability branch 2 times, most recently from 4d6f969 to 57edf1a Compare April 27, 2026 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants