Skip to content

deps: wasmtime 36.0.21 and two reviewed audit exceptions - #602

Merged
andersalm merged 1 commit into
developfrom
fix/wasmtime-36.0.21-audit
Nov 19, 2026
Merged

andersalm merged 1 commit into
developfrom
fix/wasmtime-36.0.21-audit

Conversation

@andersalm

Copy link
Copy Markdown
Contributor

Deepen notes

  1. Expert view: account for every line the resolver moved, not only wasmtime's, and check what the full runner's cargo flags really are.
  2. Raw material: develop at f6d819571; elastos/crates/elastos-compute/Cargo.toml:16 (wasmtime features, threads on); elastos/crates/elastos-compute/src/providers/component.rs:80 (the engine sets the component model and fuel only); CI's audit loop at .github/workflows/ci.yml:128; both upstream advisory pages, read directly.
  3. Methods: cargo update -p wasmtime --precise 36.0.21 per lock file, parsed lock comparison, source searches with a known positive for each, CI's audit loop over all 34 lock files, a full Linux check of the committed head and a second Linux run with --locked.
  4. Independent check: before the change both lock files fail the audit with five advisories each; after it all 34 pass. Full Linux check on the exact head: gate, test-elastos and test-capsules pass. Review by a different model family (Claude Opus): pass with notes.

Change

Eight wasmtime advisories entered the RustSec database on 19 Nov at 08:42 UTC. Five flag wasmtime 36.0.20 in elastos/Cargo.lock and capsules/object-provider/Cargo.lock, which turns the audit red and cancels every pull request's CI.

  • Lock files: wasmtime 36.0.20 to 36.0.21 in both. 31 packages move in each (the wasmtime family, pulley, winch, and cranelift 0.123.20 to 0.123.21). No manifest changes. The resolver also changed dependency references on packages whose own version did not move: 13 references across 12 packages in elastos/Cargo.lock and 12 across 11 in the object-provider lock (mostly windows-sys, plus syn for data-encoding-macro-internal and getrandom for tempfile), all inside their declared ranges and all to versions already in the lock.
  • Cleared by the bump: RUSTSEC-2026-0566, -0569, -0571, fixed in 36.0.21.
  • Two reviewed exceptions in elastos/.cargo/audit.toml: RUSTSEC-2026-0567 and -0573. The RustSec entries list no fix and no unaffected range for the 36 line. The upstream advisories list affected versions from 39.0.0 and from 47.0.0, so 36 is not affected. Each entry gives the upstream range, the link, the fact about our build, and when to remove it.
  • Reach, by source search (not a security verdict): no wasmtime-wasi or wasmtime-wasi-http in the locks, no get_module_export call, the threads feature is on, and no heap movement or reservation setting is changed.

Not verified: the advisories' exploit reproductions, macOS and Windows builds, installed-product acceptance. Compilation ran on Linux.

Follow-ups, not in this change: ask RustSec to record the unaffected ranges so the two exceptions can go; the shared full Linux runner builds without --locked.

@andersalm andersalm added this to the 2.0.2 milestone Nov 19, 2026
@andersalm
andersalm merged commit b8a3e11 into develop Nov 19, 2026
16 checks passed
@andersalm

Copy link
Copy Markdown
Contributor Author

Main: Merged on Anders's explicit authorization in chat (19 Nov). All nine required checks were green on the pull request's head.
Written by a GPT model; reviewed by Claude Opus (pass with notes) and by Root's source and receipt read, both on that same head; full Linux check passed on it.
Follow-ups: ask RustSec to record the unaffected ranges so the two exceptions can go; the shared Linux runner builds without --locked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant