CVE-2026-119141: bytecodealliance wasmtime · Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls
Affects bytecodealliance wasmtimeSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 49.0.3 or 48.0.6 when convenient.
Data as of 29 Oct 2026, 16:23 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.9 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 5.3 |
- Patch
- Available – fixed in 49.0.3, 48.0.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade bytecodealliance wasmtime to 49.0.3 or 48.0.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| bytecodealliancewasmtime | Affected
| Fixed in
|
| bytecodealliancewasmtime | Affected
| Fixed in
|
crates.iowasmtimepkg:cargo/wasmtimeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Fixed versions 48.0.6 and 49.0.3 are available and should be applied to remediate this vulnerability. Users should upgrade Wasmtime to at least version 48.0.6 or 49.0.3 depending on their current version. No other mitigations are specified.
Description
CVE-2026-119141 is a denial of service vulnerability in Wasmtime versions 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3. The flaw arises because the may_leave flag is not cleared during realloc, allowing malicious WebAssembly modules to cause the host to panic by invoking non-reentrant code via nested calls. This can crash the host by triggering reentrant calls during memory reallocation operations.