6.3

CVE-2026-34988: bytecodealliance wasmtime

CVSS: 6.3v3.1MediumAnalyzed
AliasesUBUNTU-CVE-2026-34988DEBIAN-CVE-2026-34988CGA-4vcp-m2qp-w768
Published 09-04-2026Last modified 09-04-2026

Vulnerability summary

CVE-2026-34988 is a medium (CVSS 6.3) vulnerability in bytecodealliance wasmtime. EPSS estimates a 0.30% chance of exploitation in the next 30 days, higher than 21.8% of scored vulnerabilities.

Overall risk
25/100
0100
Medium · default modelHow is this calculated?
CVSS score
6.3/10
010
Medium · v3.1 (NVD)
EPSS score
0.30%
0%100%
Low · +0.02 pp in 30 days
KEVNot listedIn no KEV catalog
RansomwareNone recordedNo known use recorded
Public exploits0No public exploits recorded

Advisory lineage

Upstream 0 · Downstream 1 · Related 2

Timeline

  1. 09-04-2026
    PublishedVulnerability first disclosed.
  2. 09-04-2026
    Last modifiedVulnerability information updated.

Description

Wasmtime is a runtime for WebAssembly. From 28.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime's implementation of its pooling allocator contains a bug where in certain configurations the contents of linear memory can be leaked from one instance to the next. The implementation of resetting the virtual memory permissions for linear memory used the wrong predicate to determine if resetting was necessary, where the compilation process used a different predicate. This divergence meant that the pooling allocator incorrectly deduced at runtime that resetting virtual memory permissions was not necessary while compile-time determine that virtual memory could be relied upon. The pooling allocator must be in use, Config::memory_guard_size configuration option must be 0, Config::memory_reservation configuration must be less than 4GiB, and pooling allocator must be configured with max_memory_size the same as the memory_reservation value in order to exploit this vulnerability. If all of these conditions are applicable then when a linear memory is reused the VM permissions of the previous iteration are not reset. This means that the compiled code, which is assuming out-of-bounds loads will segfault, will not actually segfault and can read the previous contents of linear memory if it was previously mapped. This represents a data leakage vulnerability between guest WebAssembly instances which breaks WebAssembly's semantics and additionally breaks the sandbox that Wasmtime provides. Wasmtime is not vulnerable to this issue with its default settings, nor with the default settings of the pooling allocator, but embeddings are still allowed to configure these values to cause this vulnerability. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.

CVSS metrics

9 scores · 7 sources · 2 versions

EPSS trend

Probability

0.30%

Chance of exploitation in the next 30 days

Percentile

22%

Versus all other CVEs

30-day change

+0.02 pp

From 0.29% on 21-09-2026

21-09-202621-10-2026
EPSS score
0.30%

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

Affected systems

Chainguard4 products
  • wasmcloud< 2.0.4-r0
  • wizer< 11.0.3-r10
  • yara-x< 1.15.0-r2
  • zed< 0.228.0-r3
Wolfi4 products
  • wasmcloud< 2.0.4-r0
  • wizer< 11.0.3-r10
  • yara-x< 1.15.0-r2
  • zed< 0.228.0-r3
Bytecodealliance1 product
  • wasmtime≥ 43.0.0, < 44.0.1 | ≥ 28.0.0, < 36.0.7 | ≥ 37.0.0, < 42.0.2 | 43.0.0
Crates.Io1 product
  • wasmtime≥ 28.0.0, < 36.0.7 | ≥ 37.0.0, < 42.0.2 | ≥ 43.0.0, < 43.0.1
Debian1 product
  • rust-wasmtimeAll versions (No fix recorded) | < 36.0.7+dfsg-1
Ubuntu1 product
  • rust-wasmtimeAll versions (No fix recorded)

6 vendors · 12 products

References

10 links