Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

wasmi-labs/wasmi

              main @ 8f0f8cc
            

Fixes

CVEs

HIGH

Peak severity

30.0%

Coverage

Highlights

Denial of Service: 2 prior fixes. Scrutinize any change in this area.

crates/wasmi/src/engine/executor/handler/state.rs: most-fixed (2 issues). Treat as high-risk during review.

10 high-severity fixes in this history; regressions here are high-impact.

Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Memory Safety: Host function execution can trigger linear memory growth, causing previously cached pointers to become stale and leading to a use-after-free or memory corruption when subsequent WASM code is executed. This is closely related to the behavior described in CVE-2025-66627.

Sandbox Escape: Failure to correctly track and restore active module instances during cross-instance tail calls (return_call/return_call_indirect) breaks isolation boundaries, allowing instructions to run under unauthorized contexts.

Auth Bypass: Host functions modifying tables or compiling new modules can leave the engine's translation cache (CodeView) stale, bypassing validation and safety boundaries.