Uncaught Exception Affecting wasmcloud package, versions <2.0.4-r0


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.01% (2nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Uncaught Exception vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-WASMCLOUD-16122148
  • published22 Apr 2026
  • disclosed9 Apr 2026

Introduced: 9 Apr 2026

NewCVE-2026-34944  (opens in a new tab)
CWE-248  (opens in a new tab)

How to fix?

Upgrade Chainguard wasmcloud to version 2.0.4-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream wasmcloud package and not the wasmcloud package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Wasmtime is a runtime for WebAssembly. Prior to 24.0.7, 36.0.7, 42.0.2, and 43.0.1, On x86-64 platforms with SSE3 disabled Wasmtime's compilation of the f64x2.splat WebAssembly instruction with Cranelift may load 8 more bytes than is necessary. When signals-based-traps are disabled this can result in a uncaught segfault due to loading from unmapped guard pages. With guard pages disabled it's possible for out-of-sandbox data to be loaded, but this data is not visible to WebAssembly guests. This vulnerability is fixed in 24.0.7, 36.0.7, 42.0.2, and 43.0.1.

CVSS Base Scores

version 3.1