Tested

Wasmtime still fails cargo audit: RUSTSEC-2026-0587 in wasmtime-wasi

The first November Wasmtime patches (48.0.9, 49.0.6 and 50.0.2) clear eight RustSec advisories on wasmtime, but RUSTSEC-2026-0587 on wasmtime-wasi needs the next patch: 48.0.10, 49.0.7 or 50.0.3. If your older alerts disappeared and one remains, check which package the job names. This one is on wasmtime-wasi, not wasmtime. One project's fix that moves both pins · RustSec advisory

Read the failing lockfile

Open the directory and Cargo.lock used by the failing job. If CI checks a separate plugin, example or fuzz workspace, read that lockfile too. With cargo-audit installed, its JSON report identifies both the advisory and the package version. Use your original scanner, advisory configuration and lockfile when you compare the repair.

cargo audit --json

These commands use our 48.x fixture's versions. In each command, replace 48.0.9 with the version your report names and 48.0.10 with the patched version you move to. The table below gives the first one for each line.

cargo tree --locked --workspace --target all -i wasmtime-wasi@48.0.9

The inverted tree shows the dependencies that bring in wasmtime-wasi. --workspace reads every workspace member; without it, a root that is also a package searches only its own dependencies, and a copy used only by a member exits 101 with did not match any packages. --target all can also show target-specific edges outside your current build. If your scanner reports another copy or source, check that entry separately. A tool error that prevents the scan from reading its database or lockfile leaves the finding unresolved. Cargo tree reference

Use the patch for your release line

RustSec issued the eight wasmtime entries on 19 November. Their first patched releases on lines 48, 49 and 50 are 48.0.9, 49.0.6 and 50.0.2. On 36.x, three of them are patched in 36.0.21 and the other five list 36.x as unaffected. The separate wasmtime-wasi entry was issued on 20 November and has these first patched releases.

Your lineFirst release patched for RUSTSEC-2026-0587
36.x36.0.22
48.x48.0.10
49.x49.0.7
50.x50.0.3

The 50.x range is open-ended: 50.0.3 and every later release, including 51.0.0. On other lines, such as 37 to 47, RustSec lists no patched release and no unaffected range for RUSTSEC-2026-0587, so the scan keeps reporting it until you move to a release in the table above. A scan of a release on those lines can also report other IDs. Check each remaining ID against its own advisory range. The first eight entries are 0566, 0567, 0568, 0569, 0570, 0571, 0572 and 0573.

Move coupled pins together

Read the Cargo.toml requirements from the parent in the tree. If the parent's entry says workspace = true, the requirement is in [workspace.dependencies] in the workspace root. In the crates.io index, wasmtime-wasi 48.0.10 requires wasmtime ^48.0.10, so an exact pin on wasmtime alone also holds wasmtime-wasi back. Even with caret requirements on both, cargo update -p wasmtime-wasi alone left both at 48.0.9 in our check, because wasmtime stayed locked. If the requirements already allow the patched releases, refresh the targeted lockfile entries. If a parent requires =48.0.9, a lockfile-only update cannot select 48.0.10. In our fixture this command exited 101 and Cargo named the exact requirement from plugin-host. The lockfile stayed byte-identical.

cargo update -p wasmtime-wasi@48.0.9 --precise 48.0.10

If you own the manifest with the old pins, update the coupled requirements there first. We changed both wasmtime and wasmtime-wasi from =48.0.9 to =48.0.10. If a third-party parent sets the pins, look for a compatible release of that parent which permits the patch. For a graph with one copy of each package, refresh the two entries together after checking the requirements.

cargo update -p wasmtime -p wasmtime-wasi
cargo tree --locked --workspace --target all -i wasmtime-wasi@48.0.10
cargo audit --json

If Cargo prints Locking 0 packages, no package version moved: fix the requirement first. Cargo can still rewrite other lockfile lines in that case, so check the diff before you keep it.

Review the whole lockfile diff, including sibling packages that moved with Wasmtime. If the tree or audit still names an affected copy, trace that copy in the failing job's lockfile. Run the project's normal builds and tests for the targets you ship. Cargo update reference

What the fixture showed

We used Cargo 1.99.1 and cargo-audit 0.23.0 in an official Rust Linux image pinned by digest. All four scans used the same RustSec database snapshot with no ignored advisories.

Fixture stagewasmtime and wasmtime-wasiVulnerabilities in cargo audit --jsonExit
Initial lockfile48.0.80566–0573 on wasmtime and 0587 on wasmtime-wasi1
First 48.x patch48.0.90587 on wasmtime-wasi1
Both requirements and lockfile updated48.0.1000
After a routine cargo update48.0.1000

The table lists every vulnerability the scanner reported. A plain cargo update after the repair left the fixture lockfile byte-identical.

The fixture checked dependency resolution and RustSec reporting on Linux. RustSec lists Windows as the affected OS for RUSTSEC-2026-0587, a WASI filesystem sandbox escape. cargo-audit still reported it in our Linux fixture, which set no target OS filter. Check which targets and features you ship before making claims about an application's exposure.

The Breakage Calendar checker reads a repository folder for other dated changes. It does not read Cargo.lock advisories.

Check your repository for other dated changes

Corrections can be sent to hello@cybernative.ai. We publish dated corrections.