Search results

potential gc fuzzbug: ASAN hits overflow and Segmentation fault

bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixing

fuzz-bugBugs found by a fuzzerBugs found by a fuzzer

Status: Open.

#13134 In bytecodealliance/wasmtime;

· khagankhan opened on Apr 17, 2026

Per-function compilation diagnostics in cranelift_codegen should be trace, not debug

Status: Open.

#13133 In bytecodealliance/wasmtime;

· jspaith opened on Apr 17, 2026

Functions inherit_network and allow_ip_name_lookup are missing from c-api

wasmtime:c-apiIssues pertaining to the C API.Issues pertaining to the C API.

Status: Open.

#13130 In bytecodealliance/wasmtime;

· gearhand opened on Apr 17, 2026

RUSTSEC-2026-0099: Name constraints were accepted for certificates asserting a wildcard name

Status: Open.

#13117 In bytecodealliance/wasmtime;

· github-actions opened on Apr 16, 2026

RUSTSEC-2026-0098: Name constraints for URI names were incorrectly accepted

Status: Open.

#13116 In bytecodealliance/wasmtime;

· github-actions opened on Apr 16, 2026

Should we define GC-related VM types in wasmtime-environ?

Status: Open.

#13114 In bytecodealliance/wasmtime;

· fitzgen opened on Apr 15, 2026

Deduplicate more code between DRC and copying GcCompiler implementations

wasm-proposal:gcIssues with the implementation of the gc wasm proposalIssues with the implementation of the gc wasm proposal

Status: Open.

#13113 In bytecodealliance/wasmtime;

· fitzgen opened on Apr 15, 2026

Should accesses to the GC heap use MemFlags::trusted()?

wasm-proposal:gcIssues with the implementation of the gc wasm proposalIssues with the implementation of the gc wasm proposal

Status: Open.

#13112 In bytecodealliance/wasmtime;

· fitzgen opened on Apr 15, 2026

Spurious "indirect call type mismatch" trap when calling an imported function at its actual subtype

bugIncorrect behavior in the current implementation that needs fixingIncorrect behavior in the current implementation that needs fixing

wasm-proposal:gcIssues with the implementation of the gc wasm proposalIssues with the implementation of the gc wasm proposal

Status: Open.

#13095 In bytecodealliance/wasmtime;

· shumbo opened on Apr 14, 2026

riscv64: The vxrm and vxsat registers are not preserved or handled

cranelift:area:riscv64Issues related to the RISC-V 64 backend.Issues related to the RISC-V 64 backend.

Status: Open.

#13078 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 13, 2026

riscv64: Atomics for 8/16-bit values incorrectly have two atomic loads

cranelift:area:riscv64Issues related to the RISC-V 64 backend.Issues related to the RISC-V 64 backend.

wasm-proposal:threadsIssues related to the WebAssembly threads proposalIssues related to the WebAssembly threads proposal

Status: Open.

#13076 In bytecodealliance/wasmtime;

· alexcrichton opened on Apr 13, 2026

Prefetch instruction for Cranelift

craneliftIssues related to the Cranelift code generatorIssues related to the Cranelift code generator

cranelift:area:clif

Status: Open.

#13075 In bytecodealliance/wasmtime;

· tareksander opened on Apr 13, 2026