For your digest
wasmtime-c-api-impl, wasmtime-bin: Wasmtime: Memory leak in C API with `externref` and `anyref` types
It touches something Phylax follows. No evidence of use yet.
Does it affect what I run?
Checked in your browser. The version you type is not sent anywhere.
Who is affected
- wasmtime-c-api-impl (crates.io): from 37.0.0, before 37.0.2
- wasmtime-bin (PyPI): every version, before 37.0.2
- wasmtime-bin (PyPI): every version, up to and including 37.0.0
The fix
wasmtime-c-api-impl (crates.io) fixed in 37.0.2
cargocargo update -p wasmtime-c-api-impl --precise 37.0.2Check what is installedcargo tree -i wasmtime-c-api-implPaste into Cursor, Lovable or Claude CodeUpgrade the crates.io dependency wasmtime-c-api-impl to 37.0.2 or the nearest later release, to fix CVE-2025-61670. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.wasmtime-bin (PyPI) fixed in 37.0.2
pippython -m pip install wasmtime-bin==37.0.2uvuv add wasmtime-bin==37.0.2poetrypoetry add wasmtime-bin@37.0.2Check what is installedpython -m pip show wasmtime-binPaste into Cursor, Lovable or Claude CodeUpgrade the PyPI dependency wasmtime-bin to 37.0.2 or the nearest later release, to fix CVE-2025-61670. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.
Fix commands generated from the advisory's versions. No model wrote them.
In plain words
Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.
Evidence
No evidence that it is being used, or can be. It is listed because of what it affects.
Timeline
- First published here, as "For your digest".