AIKIDO-2026-734515

TL;DR

The wasmtime-wasi crate lets a guest WASI program trigger a host panic by supplying a filesystem timestamp whose microseconds field overflows the seconds field on conversion. This reaches the WASIp1 path_filestat_set_times/fd_filestat_set_times functions and the WASIp2/WASIp3 set-times/set-times-at methods. The root cause is that Rust's Duration::new panics on overflow instead of returning an error. The fix checks for the overflow explicitly and returns an Overflow error instead of panicking.