fix(security/medium/crates/augurs-prophet): update rust crate wasmtime to v46 [security] - #508

Details

Impact

Wasmtime's allocation logic for a WebAssembly table contained checked arithmetic which panicked on overflow. This overflow is possible to trigger, and thus panic, when a table with an extremely large size is allocated. This is possible with the WebAssembly memory64 proposal where tables can have sizes in the 64-bit range as opposed to the previous 32-bit range which would not overflow. The panic happens when attempting to create a very large table, such as when instantiating a WebAssembly module or component.

This bug does not affect the pooling allocator which limits tables sizes to much less than the required amount to trigger the overflow. This bug is only present for the on-demand instance allocator, which is Wasmtime's default allocator. This bug also requires the memory64 WebAssembly feature to be enabled, which is on-by-default.

Panicking in the host process is considered a denial-of-service vector for Wasmtime.

Patches

Wasmtime 36.0.8, 43.0.2, and 44.0.1 have all been released which fixes this issue.

Workarounds

Embeddings can switch to using the pooling allocator to work around this issue, or the memory64 WebAssembly proposal can be disabled. Otherwise there is no workaround and users are recommended to upgrade.

Severity

• CVSS Score: 5.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

• https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-p8xm-42r7-89xg
• https://rustsec.org/advisories/RUSTSEC-2026-0114.html
• https://nvd.nist.gov/vuln/detail/CVE-2026-44216
• https://github.com/advisories/GHSA-p8xm-42r7-89xg

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

Details

Impact

Wasmtime's allocation logic for a WebAssembly table contained checked arithmetic which panicked on overflow. This overflow is possible to trigger, and thus panic, when a table with an extremely large size is allocated. This is possible with the WebAssembly memory64 proposal where tables can have sizes in the 64-bit range as opposed to the previous 32-bit range which would not overflow. The panic happens when attempting to create a very large table, such as when instantiating a WebAssembly module or component.

This bug does not affect the pooling allocator which limits tables sizes to much less than the required amount to trigger the overflow. This bug is only present for the on-demand instance allocator, which is Wasmtime's default allocator. This bug also requires the memory64 WebAssembly feature to be enabled, which is on-by-default.

Panicking in the host process is considered a denial-of-service vector for Wasmtime.

Patches

Wasmtime 36.0.8, 43.0.2, and 44.0.1 have all been released which fixes this issue.

Workarounds

Embeddings can switch to using the pooling allocator to work around this issue, or the memory64 WebAssembly proposal can be disabled. Otherwise there is no workaround and users are recommended to upgrade.

Severity

• CVSS Score: 5.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

• https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-p8xm-42r7-89xg
• https://nvd.nist.gov/vuln/detail/CVE-2026-44216
• https://github.com/bytecodealliance/wasmtime
• https://rustsec.org/advisories/RUSTSEC-2026-0114.html

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

Details

This is an entry in the RustSec database for the Wasmtime security advisory
located at
GHSA-p8xm-42r7-89xg
For more information see the GitHub-hosted security advisory.

Severity

• CVSS Score: 5.9 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

• https://crates.io/crates/wasmtime
• https://rustsec.org/advisories/RUSTSEC-2026-0114.html
• https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-p8xm-42r7-89xg

This data is provided by OSV and the Rust Advisory Database (CC0 1.0).

Details

This is an entry in the RustSec database for the Wasmtime security advisory
located at
GHSA-hgjw-h833-99q9
For more information see the GitHub-hosted security advisory.

Severity

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

References

• https://crates.io/crates/wasmtime
• https://rustsec.org/advisories/RUSTSEC-2026-0222.html
• https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hgjw-h833-99q9

This data is provided by OSV and the Rust Advisory Database (CC0 1.0).

v46.0.2

Compare Source

46.0.2

Released 2026-07-31.

Fixed

• Stores can mix up type indices between engines.
  GHSA-hgjw-h833-99q9

• Preemption and traps during bulk operations enable breaking internal VM state.
  GHSA-2hw9-mc66-jc2q

v46.0.1

Compare Source

46.0.1

Released 2026-06-24.

Fixed

• WASI hard links and renames check wasmtime-wasi's FilePerms for destination
  GHSA-4ch3-9j33-3pmj
• Explicit hint for generic call in wasmtime wit-bindgen.
  #​13719

v46.0.0

Compare Source

46.0.0

Released 2026-06-22.

Added

• Added opt-in support for the WebAssembly branch-hinting proposal: the
  metadata.code.branch_hint custom section is parsed and used to mark cold
  blocks during Cranelift compilation, behind Config::wasm_branch_hinting
  (off by default).
  #​13459

• Wasmtime's C API now supports type reflection of GC values.
  #​13268

• Wasmtime now supports being compiled to arm64_32 platforms.
  #​13259

• The cranelift-frontend crate,the RISC-V Cranelift backend, and Wasmtime's
  component-model-async feature now support no_std.
  #​13401
  #​13479
  #​13533

• Wasmtime has initial support for the component model (implements "...")
  feature.
  #​13361
  #​13497
  #​13513

• The wasmtime CLI now supports configuring the initial-cwd property of
  WASI.
  #​13468

• The wasmtime serve subcommand now supports --header to set headers for the
  guest.
  #​13471

• Wasmtime supports WASI 0.2.12, which notably includes exit-with-code in
  stable.
  #​13536

• Wasmtime's component-model-async-bytes feature was renamed to
  component-model-bytes and now lifting/lowering using Bytes and BytesMut
  is directly supported.
  #​13366

• Wasmtime now exposes the async call stack of components through its public API
  which can be used to determine which root task performed an import call.
  #​13510

• Wasmtime now supports WASI 0.3.0 by default and the component-model-async
  wasm feature is now enabled by default.
  #​13612

Changed

• Performance of bulk-data-transfer instructions such as
  {array,table,memory}.{copy,fill,init} have been improved.
  #​13312
  #​13367
  #​13368
  #​13382
  #​13407
  #​13424
  #​13438
  #​13460
  #​13524

• Codegen for conditions based on ctz or clz has been optimized.
  #​13332
  #​13343

• Cranelift now optimizes conditional branches of constant conditions into
  unconditional jumps.
  #​13267
  #​13391

• Wasmtime's copying collector now has an in-wasm fast path for its bump
  allocator.
  #​13323

• Wasmtime's GC implementation has been hardened in the face of GC heap
  corruption to avoid panicking or aborting. Corruption is returned as a
  WasmtimeBug type for embedders to detect and safely tear down the
  store/instance.
  #​13321
  #​13320

• Cranelift's MemFlags type is now renamed to MemFlagsData, and
  AliasRegions are now stored in the DFG.
  #​13353
  #​13354

• Wasmtime now handles OOM gracefully in more situations.
  #​13371
  #​13372
  #​13374
  #​13375
  #​13376
  #​13377
  #​13378
  #​13379
  #​13388
  #​13413
  #​13412
  #​13414

• Cranelift's egraph rewrite pass now uses a concept of fuel to avoid
  exponential blowup of rewrites.
  #​13390

• Wasmtime now consumes fuel in bulk-data-transfer instructions proportional to
  the size of the transfer.
  #​13393
  #​13448

• Cranelift's ISLE format now supports structs as well as tuple fields for
  structs/enums.
  #​13319
  #​13335

• Wasmtime's implementation of passive element and data segments is now
  optimized to perform more work in wasm itself and has a refactored
  representation on the host.
  #​13394
  #​13444

• Heuristics for triggering GC in the DRC collector have been adjusted to avoid
  blowups seen in the wild.
  #​13422

• Wasmtime's default garbage collector is now the copying collector instead of
  the deferred-reference-counting collector. This collector should be more
  performant in most situations and additionally have the ability to collect
  cycles.
  #​13439

• Wasmtime now traps if a waitable is being waited on synchronously and
  additionally added to a waitable-set.
  #​13415

• Wasmtime's behavior with subtask.cancel is now adjusted to resume the
  cancelled task immediately instead of always yielding.
  #​13443

• The wasmtime_wasi_http::handler module has had its interface overhauled to
  better handle configuring the lifecycle of a request as it flows through
  the system in terms of timeouts and such.
  #​13404

• Most of Wasmtime's instance initialization is now compiled into a per-module
  initialization function rather than happening through the host in Wasmtime.
  #​13487

• The InstanceExportLookup trait has been generalized into ExportLookup, and
  this is now optionally implemented for wit_parser::ItemName with the
  wit-parser crate feature.
  #​13505

• Many of Cranelift's *_imm instructions have been removed in favor as they
  were just sugar over other opcodes. Builder-style methods remain, however.
  #​13527
  #​13541
  #​13543
  #​13545
  #​13548
  #​13553

• Wasmtime's caching behavior is no longer gated on cfg(debug_assertions) and
  has been adjusted to handle a git source differently.
  #​13535

• Bindings generation for store-using *WithStore traits now have a type
  parameter of the store on the trait itself instead of on every method.
  #​13549

• Wasmtime now requires Rust 1.94.0 to compile.
  #​13547

Fixed

• Wasmtime's copying collector has had a few bugs related to how it's translated
  to CLIF fixed.
  #​13381

• Returning a ThrownException when there wasn't a pending exception within a
  store has been fixed.
  #​13306

• A DRC corruption issue when overwriting an i31ref slot has been fixed.
  #​13307

• Taking a store's exception from a debug handler has been fixed.
  #​13310

• Alignment checks of atomics with Winch have been fixed.
  #​13337

• GC barriers around managing the pending exception within a store have been
  fixed.
  #​13330

• Cranelift's handling of short jumps on some architectures is now improved to
  handle very large basic blocks.
  #​13392

• Cross-component stream copies have been fixed.
  #​13418

• Cranelift-generated stack maps have been fixed in a few cases.
  #​13449
  #​13466
  #​13498

• Component-to-component adapters which use resources in arguments and disable
  concurrency_support have been fixed.
  #​13542

• A panic in substituted_component_type has been fixed when guests have
  exported resources.
  #​13608

v45.0.3

Compare Source

45.0.3

Released 2026-06-24.

Fixed

• WASI hard links and renames check wasmtime-wasi's FilePerms for destination
  GHSA-4ch3-9j33-3pmj

v45.0.2

Compare Source

45.0.2

Released 2026-06-15.

Fixed

• Leak in WASIp1 fd_renumber implementation.
  GHSA-3p27-qvp9-27qf

v45.0.1

Compare Source

45.0.1

Released 2026-06-05.

Fixed

• Fixed regression with WASIp2 zero-delay clocks/timers: allow repeat calls to
  .ready() to make progress.
  #​13511

v45.0.0

Compare Source

45.0.0

Released 2026-05-21.

Added

• Winch now respects the enable_nan_canonicalization setting.
  #​12939

• Initial support for invoking component functions asynchronously has been added
  to the C API.
  #​12973

• Cranelift's s390x backend implements more instructions from z17 and also
  implements more CLIF arithmetic overflow instructions.
  #​12523
  #​12707

• Wasmtime's support for handling OOM in more APIs has expanded and is now
  documented as well.
  #​12993
  #​12988
  #​13017
  #​13047
  #​13049
  #​13051
  #​13074
  #​13083
  #​13088
  #​13224

• The Component type now offers reflection APIs over the compiled in-memory
  view of instructions in the same manner Module does.
  #​13073

• The wasmtime CLI now has a hot-blocks subcommand to explore a
  perf-recorded output and show hot basic blocks of WebAssembly instructions.
  #​13077

• Wasmtime now has an initial implementation of a copying collector for GC,
  which notably enables collecting cycles unlike the DRC collector.
  #​13093
  #​13107

• The WASI inherit_network and allow_ip_name_lookup options were added to
  the C API.
  #​13145

• The C API now has the ability to select Winch as well as the
  RegallocAlgorithm in use.
  #​13155

• The Wasmtime CLI now has a -Dmax-backtrace=N argument to control the number
  of frames captured.
  #​13218

• Wasmtime now tracks whether there are any active async tasks within a store
  and provides an embedder API to learn when there are none left.
  #​13246

• Cranelift now has an idempotent-store elimination pass.
  #​13251

Changed

• Wasmtime's DRC collector has received some optimizations to get some wins on
  local benchmarking.
  #​12969
  #​12974

• Wasmtime's C API can now be built without the gc crate feature of Wasmtime.
  #​12805

• Wasmtime now has an implemented and improved grow-vs-collect heuristic to
  improve behavior of GC-using programs.
  #​12942

• Cranelift on aarch64 now uses a more optimized frame layout for tail-call-only
  functions.
  #​11608

• Wasmtime now supports a separate set of GC tunables different from the main
  set of tunables for linear memory to enable configuring it separately.
  #​13080

• Wasmtime no longer uses pointer authentication instructions for the
  implementation of fibers due to issues on Android.
  #​13118

• Wasmtime now requires Rust 1.93.0 to compile.
  #​13127

• The behavior of using Wasmtime as a CMake subproject has been improved.
  #​13157

• Reference types in the C/C++ API have been refactored and reorganized.
  #​13154
  #​13235

• The Wasmtime CLI now warns about usage of wasi-common or wasi-threads as these
  components are slated for removal in Wasmtime 47.0.0. For more information see
  the associated RFC.
  #​13264

• Inlining in Wasmtime now has a different set of configuration options, notably
  more values are packed into -Cinlining=....
  #​13250

Fixed

• The WASIp1-to-WASIp2 adapter now handles nonblocking I/O in fd_{read,write}
  more appropriately.
  #​13111

• The Host header is injected less often for wasmtime-wasi-http.
  #​13138

• Downcasts of funcref values now uses the correct type for imported
  functions.
  #​13161

• The DRC allocator's memory usage during tracing has been reduced when there
  are large arrays.
  #​13192

• The performance of reading stdin in WASI has been improved.
  #​13256

• WASI path_open(TRUNCATE) bypasses FilePerms::WRITE host restriction.
  GHSA-2r75-cxrj-cmph

v44.0.3

Compare Source

44.0.3

Released 2026-06-15.

Fixed

• Leak in WASIp1 fd_renumber implementation.
  GHSA-3p27-qvp9-27qf

v44.0.2

Compare Source

44.0.2

Released 2026-05-21.

Fixed

• WASI path_open(TRUNCATE) bypasses FilePerms::WRITE host restriction.
  GHSA-2r75-cxrj-cmph

v44.0.1

Compare Source

44.0.1

Released 2026-04-30.

Fixed

• Panic when allocating a table exceeding the size of the host's address space.
  GHSA-p8xm-42r7-89xg

v44.0.0

Compare Source

44.0.0

Released 2026-04-20.

Added

• The wasmtime CLI now supports a -g flag which runs a built-in wasm program
  to host a gdbstub-compatible server (can be connected to with LLDB) to debug
  guest programs.
  #​12756
  #​12771
  #​12856
  #​12859

• Wasmtime now has experimental support for the map<K, V> type in the
  component model.
  #​12216

• Wasmtime's C API now supports wasm tag types.
  #​12763
  #​12803

• Wasmtime's C API now supports exceptions.
  #​12861

• Wasmtime's C API has more support for the GC proposal.
  #​12914
  #​12915
  #​12916
  #​12917

• An initial implementation of the wasi:tls proposal for the 0.3.0-draft
  version has been added.
  #​12834

Changed

• The demangle Cargo feature of the wasmtime crate is now compatible with
  no_std targets.
  #​12740

• The wasmtime-wasi-tls-* crates are now merged into one crate with feature
  flags for each backend.
  #​12780

• Wasmtime now requires Rust 1.92.0 or later to build.
  #​12828

• The cranelift-codegen crate now compiles for no_std targets.
  #​12812

• The csdb instruction, a defense-in-depth measure for spectre, is no longer
  emitted by default on aarch64 to match what peer runtimes are doing. In some
  situations this is known to provide up to a 6x performance boost on macOS as
  well.
  #​12932

Fixed

• Wasmtime's native DWARF has been improved on aarch64 to support recovering
  values more frequently.
  #​12779

• A significant number of minor issues have been fixed throughout this release.
  In addition to the security advisories found by LLMs there have also
  been a large number of other issues identified as well. Many minor fixes are
  present in this release for various situations for issues found in this
  manner.

v43.0.2

Compare Source

43.0.2

Released 2026-04-30.

Fixed

• Panic when allocating a table exceeding the size of the host's address space.
  GHSA-p8xm-42r7-89xg

v43.0.1

Compare Source

43.0.1

Released 2026-04-09.

Fixed

• Miscompiled guest heap access enables sandbox escape on aarch64 Cranelift.
  GHSA-jhxm-h53p-jm7w

• Wasmtime with Winch compiler backend may allow a sandbox-escaping memory
  access.
  GHSA-xx5w-cvp6-jv83

• Out-of-bounds write or crash when transcoding component model strings.
  GHSA-394w-hwhg-8vgm

• Host panic when Winch compiler executes table.fill.
  GHSA-q49f-xg75-m9xw

• Wasmtime segfault or unused out-of-sandbox load with f64x2.splat operator
  on x86-64.
  GHSA-qqfj-4vcm-26hv

• Improperly masked return value from table.grow with Winch compiler backend.
  GHSA-f984-pcp8-v2p7

• Panic when transcoding misaligned utf-16 strings.
  GHSA-jxhv-7h78-9775

• Panic when lifting flags component value.
  GHSA-m758-wjhj-p3jq

• Heap OOB read in component model UTF-16 to latin1+utf16 string transcoding.
  GHSA-hx6p-xpx3-jvvv

• Use-after-free bug after cloning wasmtime::Linker.
  GHSA-hfr4-7c6c-48w2

• Data leakage between pooling allocator instances.
  GHSA-6wgr-89rj-399p

• Host data leakage with 64-bit tables and Winch.
  GHSA-m9w2-8782-2946

v43.0.0

Compare Source

43.0.0

Released 2026-03-20.

Added

• Wasmtime now supports the WASIp3 snapshot 0.3.0-rc-2026-03-15.
  #​12557

• The number of frames captured in backtrace collection can now be configured.
  #​12542

• Wasmtime now supports fine-grained operator cost configuration for when fuel
  is enabled.
  #​12541

• Configuring the gc_support option is now possible through the C API.
  #​12630

• Configuring the concurrency_support option is now possible through the C
  API.
  #​12703

• Debugging-related APIs have been added to access all modules and instances on
  a store.
  #​12637

• All store entities now expose a "unique ID" for debugging purposes.
  #​12645

• Cranelift's x64 backend now supports the cls instruction for all integer
  types.
  #​12644

Changed

• Internal refactoring and support necessary for handling OOM gracefully
  throughout the runtime is proceeding apace. New APIs such as
  FuncType::try_new are available in addition to many internal changes.
  #​12530
  #​12537
  (... and many more ...)

• Wasmtime's representation of stack frames in the debugging API no longer
  borrows the store itself and is instead represented as a handle.
  #​12566

• Wasmtime now unconditionally sets SO_REUSEADDR for guest-bound sockets.
  #​12597

• Cranelift now supports more VRegs which means effectively that larger
  functions will be compilable by default rather than returning a "function too
  large" error.
  #​12611

• WASIp3 implementations now limit returned memory by default for randomness and
  HTTP headers.
  #​12745
  #​12761

Fixed

• Running wasmtime wizer over components with modules that contain an
  _initialize function no longer removes the function to preserve the validity
  of the component.
  #​12540

• Borrow state for host async tasks is now handled more correctly throughout
  Wasmtime, especially in the face of cancellation.
  #​12550

• Bindings generation now accounts for the fact that future and stream are
  not cloneable types.
  #​12155

• The impementation of UDP in WASIp2 has had some wakeup-related bugs fixed.
  #​12629

• Cancellation of host subtasks for component-model-async has been improved and
  works more reliably.
  #​12640

• Subtask management for component-model-async now no longer reparents which
  fixes a number spec-related divergences.
  #​12570

• Converting a wasmtime::Error into anyhow::Error and using downcast has
  been fixed.
  #​12689

• Async stream/future read/write cancellation has had some corner cases fixed.
  #​12704

• Cranelift's timing infrastructure is now more robust in the face of buggy
  system clocks.
  #​12709

• The currently running guest task has been corrected in a number of cases
  related to component-model-async and cooperative threading.
  #​12718
  #​12735
  #​12736
  #​12737

• An issue of lost wakeups with the WASIp3 stdin implementation has been fixed.
  #​12745