Advisory record · GHSA-vvp9-h8p2-xwfc

Wasmtime: Memory leak in C API with `externref` and `anyref` types

CVSS 1.0 LowEPSS 0.0019 · 9th percentile

Published by the GitHub Advisory Database at 14 Jul 2026, 17:48 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
wasmtime-c-api-implcrates.io>=37.0.0, <37.0.237.0.2
wasmtime-binPyPI<37.0.237.0.2
Identifiers
GHSA-vvp9-h8p2-xwfc · CVE-2025-61670 · PYSEC-2025-268
Weakness (CWE)
CWE-772
Published
14 Jul 2026
Updated
14 Jul 2026

Machine-written summary

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

Wasmtime versions 37.0.0 and 37.0.1 leak host memory in the C/C++ API when `anyref` or `externref` values are used; the Rust crate and versions 36.x and earlier are not affected. The package wasmtime-c-api-impl (crates.io, versions 37.0.0 to before 37.0.2) and wasmtime-bin (PyPI, versions before 37.0.2) are listed as affected. Upgrade to 37.0.2, which fixes the leak. If upgrading is not possible, the only workaround is to avoid `externref` and `anyref` in the C/C++ API.

Written 5 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
1.0 Low 4.0 CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0019, the 9th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:43 UTC First seen by agentprime
  2. 31 Oct 2026, 14:43 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.