{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-47218 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-47218 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47218 is a critical unsafe deserialization vulnerability in containerd runwasi, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47218 and fix it if it is affected.\n\nWhat it is: CVE-2026-47218 is a critical unsafe deserialization vulnerability in containerd runwasi, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47218 in the wild and no public exploit code.\n\nAffected product: containerd runwasi. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-47218/ (Markdown: https://insights.sbomify.com/CVE-2026-47218/index.md)","id":"CVE-2026-47218","markdown":"https://insights.sbomify.com/CVE-2026-47218/index.md","name":"CVE-2026-47218","record":{"aliases":["GHSA-cc25-vq59-rcjx"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"containerd runwasi shim","requires_auth":"none","summary":"Attackers can execute native code by forging Wasmtime precompiled OCI layers, bypassing the WASI sandbox in containerd runwasi shims.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"runwasi facilitates running Wasm and WASI workloads managed by containerd. Prior to 0.6.1, containerd-shim-wasmtime-v1 can treat Wasmtime precompiled bytes supplied directly in an OCI image layer as a trusted artifact from the precompile-cache path and deserialize them as native code. An attacker who causes a victim to run a crafted image can bypass WebAssembly validation and execute native code in the shim zygote process, gaining the filesystem, environment, credentials, networking, and Linux syscall access available to the workload container. Downstream shims built with runwasi's containerd-shim-wasm precompile-cache API are also affected if they implement Compiler and trust executable precompiled artifacts from OCI image layers; the 0.6.1 boundary applies specifically to containerd-shim-wasmtime and does not independently certify downstream product releases. The flaw escapes the WASI sandbox to the workload container boundary, but it does not by itself bypass container isolation or provide direct host code execution. This issue is fixed in version 0.6.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"runwasi: Forged Wasmtime precompiled OCI layer bypasses runwasi WASI sandbox","id":"CVE-2026-47218","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"find-my-way is Vulnerable to DDoS with HTTP2","id":"CVE-2026-47219"},"packages":[],"prev":{"headline":"Typesense: Unauthenticated Denial of Service in the Typesense /multi_search Endpoint","id":"CVE-2026-47216"},"products":["runwasi"],"published":"2026-10-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["containerd"]},"summary":"Attackers can execute native code by forging Wasmtime precompiled OCI layers, bypassing the WASI sandbox in containerd runwasi shims.","url":"https://insights.sbomify.com/CVE-2026-47218/"}