Skip to main content
VulnerabilityPublished

CVE-2026-126409: bytecodealliance wasmtime · Type Confusion

Affects bytecodealliance wasmtimeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 1.8 Low : upgrade to 48.0.8 when convenient.

Data as of 13 Nov 2026, 09:44 UTC

CVSS 4.0 base score
1.8Low
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.01.8
CNA (VulnCheck)CVSS 3.12.0
Patch
Available – fixed in 48.0.8, 49.0.5, 50.0.1
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 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 13 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
bytecodealliancewasmtimeAffected
  • >=47.0.0 <48.0.8
Fixed in
  • 48.0.8
bytecodealliancewasmtimeAffected
  • >=49.0.0 <49.0.5
Fixed in
  • 49.0.5
bytecodealliancewasmtimeAffected
  • >=50.0.0 <50.0.1
Fixed in
  • 50.0.1
crates.iowasmtimepkg:cargo/wasmtimeOther threatsAffected
  • >=47.0.0 <48.0.8
  • >=49.0.0 <49.0.5
  • >=50.0.0 <50.0.1
Fixed in
  • 48.0.8
  • 49.0.5
  • 50.0.1

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

Description

Wasmtime 47.0.0 before 48.0.8, 49.0.0 before 49.0.5, and 50.0.0 before 50.0.1 contains a cross-engine type confusion vulnerability because StructType::with_finality_and_supertype does not validate that the supplied supertype belongs to the same Engine. Embedders using multiple engines that create a GC struct type with another engine's supertype can trigger runtime panics or GC heap corruption, causing denial of service; guest WebAssembly cannot trigger it.

References

Community reviews

Loading reviews…