build(deps): bump wasmtime 44.0.3 → 45.0.3 for RUSTSEC-2026-0188 (#632)#633
Merged
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Rivet Criterion Benchmarks'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: 171743e | Previous: 69960d8 | Ratio |
|---|---|---|---|
store_insert/10000 |
16109658 ns/iter (± 913795) |
12609597 ns/iter (± 589531) |
1.28 |
This comment was automatically generated by workflow using github-action-benchmark.
RUSTSEC-2026-0188: WASI hard links and renames bypass wasmtime-wasi's FilePerms on the destination path. Our pinned 44.0.3 is affected; the fix landed in 45.0.3 / 46.0.1. Pin to >=45.0.3 (stay <46 to minimize churn). The 44->45 bump is source-compatible — `rivet-core --features wasm` (the only wasmtime user, src/wasm_runtime.rs) compiles unchanged and all 13 wasm_runtime tests pass. `cargo audit` no longer reports RUSTSEC-2026-0188. Same maintenance class as #542 (43->44 for RUSTSEC-2026-0182, carried by 45.x). Refs: REQ-086 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
avrabe
force-pushed
the
fix/rustsec-2026-0188-wasmtime
branch
from
7157a5c to
171743e
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Bumps
wasmtime/wasmtime-wasi44.0.3 → 45.0.3 to resolve RUSTSEC-2026-0188 (WASI hard-link/rename FilePerms bypass on the destination path), currently failing the Security Audit (RustSec) gate onmainand every PR. Closes #632.Why now
The advisory affects our pinned 44.0.3 and would ship in the next release. rivet's only wasmtime user is
rivet-core/src/wasm_runtime.rs(compose-witness runner,wasmfeature) — the witness/MC-DC surface that matters to the ASIL-D downstream (gale).Validation
cargo build -p rivet-core --features wasmcompiles unchanged.wasm_runtimetests pass under--features wasm.cargo auditno longer reports RUSTSEC-2026-0188.🤖 Generated with Claude Code