Advisory record · GHSA-2hw9-mc66-jc2q

Preemption and traps during bulk operations enable breaking internal VM state

CVSS 2.0 LowEPSS 0.0028 · 20th percentile

Published by the maintainers · not yet reviewed by GitHub. The bytecodealliance/wasmtime maintainers published this as a GitHub repository advisory; GitHub’s reviewed advisory replaces it here when it arrives.

Published by the bytecodealliance/wasmtime maintainers at 31 Jul 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
wasmtimecrates.io>=46.0.0, <46.0.2 || >=47.0.0, <47.0.346.0.2, 47.0.3
Identifiers
GHSA-2hw9-mc66-jc2q · CVE-2026-104855 · RUSTSEC-2026-0223
Weakness (CWE)
CWE-362
Published
31 Jul 2026
Updated
12 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Wasmtime versions 46.0.0 to before 46.0.2 and 47.0.0 to before 47.0.3 are affected. The source gives few details beyond a title describing preemption and traps during bulk operations that can break internal VM state, and it does not say what access an attacker needs. Upgrade to Wasmtime 46.0.2 or 47.0.3, depending on the release line in use.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.0 Low 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0028, the 20th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Jul 2026, 16:23 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:24 UTC First seen by agentprime
  3. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.