Critical CVE-2026-47218 Allows Native Code Execution in Runwasi Before Version 0.6.1

The runwasi project has released version 0.6.1 to address a critical security vulnerability, identified as CVE-2026-47218, that allows unauthorized native code execution. This flaw exists in versions of the software prior to the 0.6.1 release and impacts the containerd-shim-wasmtime-v1 component.

The issue arises because the shim incorrectly treats WebAssembly precompiled bytes supplied directly in an OCI image layer as trusted artifacts. According to the National Vulnerability Database record, the system deserializes these bytes as native code from the precompile-cache path. This behavior bypasses standard WebAssembly validation checks.

Technical Context and Impact

An attacker who causes a victim system to run a crafted container image can exploit this deserialization flaw. The attacker gains the ability to execute native code within the shim zygote process. This execution occurs with the same filesystem, environment, credentials, networking, and Linux syscall access available to the workload container itself.

The vulnerability is classified with a CVSS score of 9.3, which is rated as Critical. It is associated with CWE-502, which pertains to deserialization of untrusted data. The flaw allows an escape from the WASI sandbox boundary into the workload container boundary. However, the source material clarifies that this issue does not by itself bypass container isolation. It also does not provide direct code execution on the host system.

Scope and Affected Components

The primary affected component is containerd-shim-wasmtime-v1 in runwasi versions earlier than 0.6.1. The fix is confirmed only for this specific version boundary. Downstream shims built using runwasi's containerd-shim-wasm precompile-cache API may also be affected. These downstream products are vulnerable if they implement the Compiler interface and trust executable precompiled artifacts from OCI image layers.

The 0.6.1 boundary applies specifically to the containerd-shim-wasmtime component. It does not independently certify the security status of downstream product releases. Organizations using custom or downstream shims must verify their own implementations against the described trust assumptions.

What should you do?

Users of runwasi should immediately check their current version and upgrade to 0.6.1 or later if they are running affected versions. Administrators should audit their container images for any use of precompiled WebAssembly bytes in OCI layers. Teams should review their trust models for downstream shims that utilize the precompile-cache API. Security teams should monitor for any active exploitation attempts targeting this deserialization flaw.