# Stores can mix up type indices between engines

Advisory record · `GHSA-hgjw-h833-99q9`

- **Identifiers:** `GHSA-hgjw-h833-99q9` · `CVE-2026-115393` · `RUSTSEC-2026-0222`
- **State:** Confirmed
- **Severity:** CVSS 1.0 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-787](https://cwe.mitre.org/data/definitions/787.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Published:** 31 Jul 2026
- **Updated:** 24 Oct 2026
- **Reviewed by a person:** No

[Published by the maintainers](https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hgjw-h833-99q9) · 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.

## Affected packages

- `wasmtime` (crates.io): affected `>=0.0.0-0, <24.0.12 || >=25.0.0, <36.0.13 || >=37.0.0, <46.0.2 || >=47.0.0, <47.0.3`; fixed in `24.0.12`, `36.0.13`, `46.0.2`, `47.0.3`

## Machine-written summary

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

> Wasmtime versions before 24.0.12, from 25.0.0 before 36.0.13, from 37.0.0 before 46.0.2, and from 47.0.0 before 47.0.3 are affected. The source gives few details: it only points to the GitHub-hosted advisory for the nature of the flaw. Upgrade to 24.0.12, 36.0.13, 46.0.2, 47.0.3, or a later patched release.

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

- 1.0 Low, CVSS 4.0: `CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0009, the 1st percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Jul 2026, 16:23 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hgjw-h833-99q9)
- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0222)

## Sources

- [GitHub Advisory Database: GHSA-hgjw-h833-99q9](https://github.com/advisories/GHSA-hgjw-h833-99q9)
- [OSV: GHSA-hgjw-h833-99q9](https://osv.dev/vulnerability/GHSA-hgjw-h833-99q9)
- <https://crates.io/crates/wasmtime>
- <https://rustsec.org/advisories/RUSTSEC-2026-0222.html>
- <https://github.com/bytecodealliance/wasmtime/pull/14044>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-hgjw-h833-99q9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hgjw-h833-99q9/>. Everything for agents: <https://agentprime.io/llms.txt>.