Skip to main content
VulnerabilityPublished

CVE-2026-119142: bytecodealliance wasmtime · Reachable Assertion

Affects bytecodealliance wasmtimeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 49.0.3 or 48.0.6 when convenient.

Data as of 29 Oct 2026, 16:23 UTC

CVSS 4.0 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.9
CNA (VulnCheck)CVSS 3.14.8
Patch
Available – fixed in 49.0.3, 48.0.6
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
bytecodealliancewasmtimeAffected
  • >=49.0.0 <49.0.3
Fixed in
  • 49.0.3
bytecodealliancewasmtimeAffected
  • >=46.0.0 <48.0.6
Fixed in
  • 48.0.6
crates.iowasmtimepkg:cargo/wasmtimeOther threatsAffected
  • >=46.0.0 <48.0.6
  • >=49.0.0 <49.0.3
Fixed in
  • 48.0.6
  • 49.0.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade wasmtime to version 48.0.6 or later, or 49.0.3 or later, where this issue has been fixed. No other mitigation is required as the vulnerability is resolved in these fixed versions.

Description

CVE-2026-119142 is a denial of service vulnerability in wasmtime versions 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3. Dropping the Future returned by TypedFunc::call_async when the guest task has not started causes cleanup code to unwrap an error, leading to a panic that crashes the host application.

References

Community reviews

Loading reviews…