Skip to navigation

Threat reportVulnerabilityTL-2026-4521

Wasmtime Cranelift Sandbox Escape Flaws (CVE-2026-115889, CVE-2026-115893)

criticalPATCHED

Two critical (CVSS 9.9) Wasmtime/Cranelift miscompilation flaws allow a crafted WebAssembly module to escape the sandbox: a silent overflow of bit-packed SSA value indices (all architectures, CVE-2026-115889) and an incorrect conditional branch target for very large br_table instructions on aarch64 (CVE-2026-115893). First disclosed .

Key facts for Wasmtime Cranelift sandbox escape

IdentifiersTL-2026-4521, CVE-2026-115889, CVE-2026-115893
Also known asGHSA-897f-g5gm-fmxm, GHSA-mghf-wjfp-p5xm, RUSTSEC-2026-0380, RUSTSEC-2026-0379
SeverityCRITICAL
CVSS9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H)
First disclosed
Exploitation statusNo exploitation observed (theoretical)
EPSSCVE-2026-115893: 0.9% (62.6th percentile); CVE-2026-115889: 0.4% (39.4th percentile)
Affected productsBytecode Alliance Wasmtime (Cranelift backend), CVE-2026-115889; Bytecode Alliance Wasmtime / Cranelift on aarch64, CVE-2026-115893; Debian wasmtime package
Weaknesses (CWE)CWE-197, CWE-843, CWE-691
Toolscargo-audit
MITRE ATT&CK techniquesT1190 Exploit Public-Facing Application, T1203 Exploitation for Client Execution, T1611 Escape to Host
MotivationUNKNOWN
Target sectorstechnology, cloud services, telecoms, software development
Target regionsGlobal
Detection rules9 (1 shown free)
Sources7 cited sources

Detection coverage for Wasmtime Cranelift sandbox escape

As of 2026-10-27, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-4521 across Splunk SPL, Microsoft KQL and Sigma, covering 10 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Wasmtime Process Spawning Shell or Download Tooling - Post-Sandbox-Escape (T1611)

Detects a wasmtime process as the parent of a shell, interpreter or network tool. The Wasmtime CLI and well-behaved embedders do not spawn such children, and a Wasm guest cannot do so inside the sandbox, so this is a strong post-escape indicator for CVE-2026-115889 / CVE-2026-115893 (Escape to Host, T1611). Process-level behaviour is inferred from the vulnerability class, not from an observed exploit.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1611, T1059.004, T1068
  • Data sources: sysmon for linux (EventCode 1), MDE DeviceProcessEvents, linux process_creation
  • Severity: critical
  • Confidence: high

Splunk SPL

index=linux sourcetype="sysmon:linux" EventCode=1 ParentImage="*/wasmtime" Image IN ("*/sh", "*/bash", "*/dash", "*/zsh", "*/curl", "*/wget", "*/nc", "*/ncat", "*/socat", "*/python*", "*/perl", "*/busybox")
| stats count min(_time) AS first_seen max(_time) AS last_seen values(CommandLine) AS cmdlines dc(Image) AS distinct_children BY host, User, ParentImage
| convert ctime(first_seen) ctime(last_seen)

Microsoft KQL

DeviceProcessEvents
| where Timestamp > ago(24h)
| where InitiatingProcessFileName =~ 'wasmtime'
| where FileName in~ ('sh', 'bash', 'dash', 'zsh', 'curl', 'wget', 'nc', 'ncat', 'socat', 'perl', 'busybox') or FileName startswith 'python'
| project Timestamp, DeviceName, AccountName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine

Sigma

title: Wasmtime Process Spawning Shell or Network Tool
id: 2f8a6d91-0b4c-4e37-9a52-c18d73e5b604
status: experimental
description: Detects the wasmtime runtime spawning a shell, interpreter or download/network utility. Indicates possible Wasm sandbox escape (CVE-2026-115889, CVE-2026-115893).
references:
    - https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-897f-g5gm-fmxm
    - https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-mghf-wjfp-p5xm
author: AII-Detector — ThreadLinqs Intelligence
date: 2026/10/27
tags:
    - attack.privilege-escalation
    - attack.t1611
    - attack.t1068
    - attack.execution
    - attack.t1059.004
    - cve.2026-115889
    - cve.2026-115893
logsource:
    product: linux
    category: process_creation
detection:
    selection_parent:
        ParentImage|endswith: '/wasmtime'
    selection_child:
        Image|endswith:
            - '/sh'
            - '/bash'
            - '/dash'
            - '/zsh'
            - '/curl'
            - '/wget'
            - '/nc'
            - '/ncat'
            - '/socat'
            - '/perl'
            - '/busybox'
    selection_python:
        Image|contains: '/python'
    condition: selection_parent and (selection_child or selection_python)
falsepositives:
    - Custom embedders that intentionally launch helper processes
    - Developer or CI wrappers that invoke wasmtime through a shell script
level: high

Known false positives:

  • Custom embedders that intentionally launch helper processes
  • CI or developer wrappers where a shell script is the wasmtime parent
  • Debugging sessions that attach tooling to wasmtime

Tuning notes: Add the names of in-house embedder binaries to the parent match. Allowlist known helper children by full command line, not by image. Raise priority when the host runs untrusted tenant modules or has the aarch64 architecture.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Precompiled [indicator] .cwasm Artifact Written to Untrusted Writable Path (CVE-2026-115889 / CVE-2026-115893) · unlock with TL Creds
  • [indicator] Process Launching Container/Namespace Escape Tooling (T1611) · unlock with TL Creds
  • [indicator] Process Periodic Beaconing to a Public IP (Post-Escape C2 Candidate) · unlock with TL Creds
  • [indicator] Executing Precompiled Module from Writable Directory with --allow-precompiled · unlock with TL Creds
  • [indicator] Process Writing Persistence or Privilege Files on Host · unlock with TL Creds
  • [indicator] Process Connecting to Public IP on Common C2 or Non-Standard Ports · unlock with TL Creds
  • [indicator] Host Process Crash (SIGSEGV/SIGILL) - Possible Cranelift Miscompilation Exploit Attempt (CVE-2026-115889 / CVE-2026-115893) · unlock with TL Creds
  • [indicator] Process Outbound Connection to Public IP - Post-Escape C2 or Staging (CVE-2026-115889 / CVE-2026-115893) · unlock with TL Creds

Indicators of compromise for Wasmtime Cranelift sandbox escape

As of 2026-10-27, Threadlinqs Intelligence tracks 10 indicators of compromise for TL-2026-4521.

10 indicators of compromise · unlock with TL Creds. Compare plans

How Wasmtime Cranelift sandbox escape works

Patched in 36.0.19, 48.0.7, 49.0.4 and 50.0.0/43.0.0+; no in-the-wild exploitation, public PoC or CISA KEV listing reported as of 2026-10-26.

Wasmtime is the Bytecode Alliance's WebAssembly runtime, and Cranelift is its default compiler backend. Both vulnerabilities are compiler correctness bugs: a malicious but syntactically valid Wasm module causes Cranelift to emit machine code that violates the sandbox's memory/control-flow isolation guarantees. Embedders that compile or load untrusted Wasm (multi-tenant serverless/edge platforms, plugin hosts) are the exposed population.

CVE-2026-115889 (GHSA-897f-g5gm-fmxm, RUSTSEC-2026-0380; CWE-197 Numeric Truncation Error, CWE-843 Type Confusion) stems from Cranelift bit-packing SSA value indices into a 24-bit field in a way that silently overflows in release builds. Specially crafted modules with very large function bodies cause value references in the intermediate representation to alias the wrong values, producing type confusion and arbitrary miscompilation that can lead to sandbox escape on all architectures using the default Cranelift settings. Affected: Wasmtime before 36.0.19 and 37.0.0 up to (not including) 43.0.0. Wasmtime 43 fixed it by moving to full u32 indexing with explicit overflow limits (PR #12613); the 36.x LTS line received a backport in 36.0.19.

CVE-2026-115893 (GHSA-mghf-wjfp-p5xm, RUSTSEC-2026-0379; CWE-691 Insufficient Control Flow Management) affects only aarch64. When a Wasm br_table instruction has more than roughly 256,000 targets, the default-branch conditional offset is out of range and wraps, so the emitted branch jumps to an incorrect target at an attacker-controlled offset in other code. Per the advisory this affects aarch64 deployments since Cranelift's initial aarch64 support in 2020. Affected: before 36.0.19, 37.0.0 to before 48.0.7, and 49.0.0 to before 49.0.4 (fix in PR #14826).

Both carry CVSS v3.1 9.9 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H per the CVE-2026-115889 advisory), published by GitHub as CNA around 2026-10-19 to 2026-10-23. Credited researchers: jaydns (CVE-2026-115889, reported with AI assistance) and ilyas-mallah (CVE-2026-115893). SOCRadar reports no public PoC and no in-the-wild exploitation as of 2026-10-26, and neither CVE is in CISA KEV; it notes that the public fixes expose the vulnerable compiler paths, raising urgency for platforms handling untrusted Wasm. Machine code already compiled by a vulnerable Cranelift (for example cached or precompiled .cwasm artifacts) retains the miscompilation, so remediation requires upgrading, rebuilding embedders and recompiling cached modules. No configuration workaround is documented; upgrading is the sole mitigation. Debian trixie (26.0.1) and sid (36.0.13) packages were listed as vulnerable/unfixed at the time of the Debian tracker snapshot.

MITRE ATT&CK techniques by tactic:

Initial Access

T1190 Exploit Public-Facing Application

Execution

T1203 Exploitation for Client Execution

Privilege Escalation

T1611 Escape to Host

Remediation for Wasmtime Cranelift sandbox escape

Patches

  • Wasmtime 36.0.19 (LTS backport, both CVEs)
  • Wasmtime 43.0.0 and later (CVE-2026-115889)
  • Wasmtime 48.0.7, 49.0.4 and 50.0.0 (CVE-2026-115893)

Immediate actions

  • Upgrade Wasmtime to a fixed release: 36.0.19, 48.0.7, 49.0.4 or 50.0.0 (CVE-2026-115889 is also fixed in 43.0.0+)
  • Rebuild and redeploy every application that embeds Wasmtime/Cranelift
  • Recompile all cached or precompiled Wasm modules, since machine code from a vulnerable compiler retains the miscompilation
  • Prioritize multi-tenant and edge/serverless platforms that compile untrusted Wasm, and aarch64 hosts for CVE-2026-115893

Workarounds

  • No configuration workaround documented; upgrading is the sole mitigation

Longer-term hardening

  • Run cargo-audit in CI against RUSTSEC-2026-0379 and RUSTSEC-2026-0380 and refresh lockfiles
  • Defense-in-depth for untrusted Wasm: run runtimes in separate OS-level sandboxes (container/VM, seccomp, least-privilege users)
  • Do not accept precompiled Wasm artifacts from untrusted sources; compile in a trusted pipeline

Affected and fixed versions

  • Bytecode Alliance — Wasmtime (Cranelift backend), CVE-2026-115889
    Vulnerable versions: < 36.0.19; >= 37.0.0, < 43.0.0
    Fixed in: 36.0.19; 43.0.0 and later
  • Bytecode Alliance — Wasmtime / Cranelift on aarch64, CVE-2026-115893
    Vulnerable versions: < 36.0.19; >= 37.0.0, < 48.0.7; >= 49.0.0, < 49.0.4
    Fixed in: 36.0.19; 48.0.7; 49.0.4; 50.0.0
  • Debian — wasmtime package
    Vulnerable versions: trixie 26.0.1+dfsg-3; sid/forky 36.0.13+dfsg-1

Timeline of Wasmtime Cranelift sandbox escape

  • Cranelift gains initial aarch64 support in 2020; the advisory states CVE-2026-115893 affects aarch64 deployments since then (exact day not given by source).
  • Both flaws reported to the locked-ioc-8 project (locked-ioc-10 for CVE-2026-115889 with AI assistance; locked-ioc-5 for CVE-2026-115893); GitHub advisories GHSA-897f-g5gm-fmxm and GHSA-mghf-wjfp-p5xm dated this day.
  • RUSTSEC-2026-0380 issued for CVE-2026-115889 (modified 2026-10-24).
  • CVE-2026-115889 and CVE-2026-115893 published by GitHub as CNA, both CVSS v3.1 9.9; patches released in 36.0.19, 48.0.7, 49.0.4 and 50.0.0.
  • As of this date SOCRadar reports no in-the-wild exploitation, no public PoC and no CISA KEV listing.
  • SOCRadar publishes analysis highlighting urgency for multi-tenant platforms running untrusted WebAssembly.

Sources cited for Wasmtime Cranelift sandbox escape

Previous and next in vulnerability

Drafted by the Threadlinqs research pipeline from 7 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

[ 0 threats ] [ 0 det ] [ CRIT: 0 ] [ HIGH: 0 ]
// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats