← Back
UBUNTU-CVE-2026-24116
Vulnerability in rust-wasmtime (UBUNTU-CVE-2026-24116)
Summary
vulnerability in rust-wasmtime (UBUNTU-CVE-2026-24116). Risk of unauthorized operations or information disclosure. Exploitable via ``f64.copysign``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2026-24116** has been found in rust-wasmtime.
Attackers can target a specific entry point like ``f64.copysign`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "rust-wasmtime UBUNTU-CVE-2026-24116" on the vendor's site.
UBUNTU-CVE-2026-24116 (rust-wasmtime) —
Attack vector: local / unauthenticated
Attack surface: `f64.copysign`
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** (unclassified) exists in rust-wasmtime. Attackers reach the vulnerable code path via ``f64.copysign`` without authentication.
📍 Affected scope
rust-wasmtime — . Attack surface: `f64.copysign`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ 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 'rust-wasmtime' .` 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 'rust-wasmtime' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `rust-wasmtime` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:24.04:LTS
rust-wasmtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:25.10
rust-wasmtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:26.04:LTS
rust-wasmtime
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- report https://ubuntu.com/security/CVE-2026-24116
- report https://www.cve.org/CVERecord?id=CVE-2026-24116
- report https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-vc8c-j3xm-xj73
- report https://github.com/bytecodealliance/wasmtime/commit/ac92d9bb729ad3a6d93f0724c4c33a0c4a9c0227
- report https://github.com/bytecodealliance/wasmtime/commit/728fa07184f8da2a046f48ef9b61f869dce133a6
- report https://github.com/bytecodealliance/wasmtime/commit/799585fc362fcb991de147dd1a9f2ba0861ed440
- report https://rustsec.org/advisories/RUSTSEC-2026-0006.html
- report https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.memory_guard_size
- report https://docs.rs/wasmtime/latest/wasmtime/struct.Config.html#method.signals_based_traps
- report https://docs.wasmtime.dev/stability-release.html