Stream: git-wasmtime

Topic: wasmtime / issue #14046 Consider adding an engine asserti...

Wasmtime GitHub notifications bot (Jul 31 2026 at 15:24):

alexcrichton opened issue #14046:

This is a follow-up to https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hgjw-h833-99q9 and https://github.com/bytecodealliance/wasmtime/pull/14044 which wasn't originally included in the fix for the advisory due to complexity needed. The idea though is that it might be reasonable to have a defensive assertion in Module::wasm_to_array_trampoline to assert that the engine which the VMSharedTypeIndex comes from is indeed the same engine as the Module itself.

@fitzgen one possible idea I just had from the original implementation you had was that we could perhaps store an "Engine ID" inside of a ModuleRegistry to avoid threading &Engine to a whole bunch of new places if that causes problems. That'd be easier than storing the entire engine itself in there.

Wasmtime GitHub notifications bot (Aug 13 2026 at 16:31):

fitzgen added the cleanup label to Issue #14046.

Last updated: Aug 30 2026 at 09:07 UTC