← Back
CVE-2025-61670
Vulnerability in wasmtime-c-api-impl (CVE-2025-61670)
Summary
vulnerability in wasmtime-c-api-impl (CVE-2025-61670). Risk of unauthorized operations or information disclosure. Exploitable via ``anyref``. Mitigation: upgrade to `37.0.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-61670** has been found in wasmtime-c-api-impl.
Attackers can target a specific entry point like ``anyref`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade wasmtime-c-api-impl to **37.0.2** or later.
If unsure, ask your IT team or search "wasmtime-c-api-impl CVE-2025-61670" on the vendor's site.
CVE-2025-61670 (wasmtime-c-api-impl) — CWE-772 /
Attack vector: local / no user interaction
Attack surface: `anyref` / `externref` / `wasmtime` / `wasmtime_store_t`
Patched: `37.0.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-772) exists in wasmtime-c-api-impl. Attackers reach the vulnerable code path via ``anyref`` without authentication.
📍 Affected scope
wasmtime-c-api-impl — . Attack surface: `anyref` / `externref` / `wasmtime` / `wasmtime_store_t`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **37.0.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'wasmtime-c-api-impl' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'wasmtime-c-api-impl' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `wasmtime-c-api-impl` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade wasmtime-c-api-impl to 37.0.2ステージング環境で 37.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
wasmtime-c-api-impl
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"37.0.2"}]}]
pip
wasmtime-bin
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"37.0.2"}]}]
PyPI
wasmtime-bin
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"37.0.0"},{"last_affected":"37.0.1"}]}]
References
- advisory https://github.com/bytecodealliance/wasmtime/releases/tag/v37.0.2
- patch https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-vvp9-h8p2-xwfc
- patch https://github.com/bytecodealliance/wasmtime/commit/adff9d9d0f09569203709d5687e5a7dc8e1ad0a3
- web https://nvd.nist.gov/vuln/detail/CVE-2025-61670
- web https://github.com/pypa/advisory-database/tree/main/vulns/wasmtime-bin/PYSEC-2025-268.yaml
- web https://github.com/advisories/GHSA-vvp9-h8p2-xwfc