Wasmtime Cranelift aarch64 br_table Incorrect Branch Target (CVE-2026-115893)
Detects the presence and exploitation risk of CVE-2026-115893, a control-flow integrity flaw (CWE-691) in the Wasmtime WebAssembly runtime's Cranelift code generator on aarch64. When compiling a Wasm module containing a br_table instruction with more than about 256,000 targets, the aarch64 backend can emit a branch that jumps to an incorrect target, leading to sandbox escape and arbitrary control flow within the host process. The flaw is tracked in GHSA-mghf-wjfp-p5xm. Affected: wasmtime < 36.0.19, >= 37.0.0 < 48.0.7, and >= 49.0.0 < 49.0.4. This detection surfaces vulnerable Wasmtime binaries and crates on aarch64 hosts, untrusted-module compilation activity, and anomalous crashes or control-flow faults in processes embedding Wasmtime.
Vulnerability Intelligence
TheoreticalAffected Software
- Vendor
- rust
- Product
- wasmtime
- Versions
- < 36.0.19, >= 37.0.0, < 48.0.7, >= 49.0.0, < 49.0.4
Weakness (CWE)
Timeline
- Disclosed
- October 28, 2026
References & Proof of Concept
- https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-mghf-wjfp-p5xm
- https://nvd.nist.gov/vuln/detail/CVE-2026-115893
- https://github.com/bytecodealliance/wasmtime/pull/14818
- https://github.com/bytecodealliance/wasmtime/pull/14819
- https://github.com/bytecodealliance/wasmtime/pull/14820
- https://github.com/bytecodealliance/wasmtime/pull/14826
- https://github.com/bytecodealliance/wasmtime/commit/222ff3a65dab9aa7011f8c246937751a0bac5abd
- https://github.com/bytecodealliance/wasmtime/commit/994549891c8a706cb4f2809f9d17b9f67b31e618
- https://github.com/bytecodealliance/wasmtime/commit/e61df1b454be9313d61a5f8de07722a421139bbe
- https://github.com/bytecodealliance/wasmtime/commit/f517bd6e890c7c1291ab9fe05d8cc0c9f11e56aa
- https://github.com/bytecodealliance/wasmtime/releases/tag/v36.0.19
- https://github.com/bytecodealliance/wasmtime/releases/tag/v48.0.7
- https://github.com/bytecodealliance/wasmtime/releases/tag/v49.0.4
- https://rustsec.org/advisories/RUSTSEC-2026-0379.html
- https://github.com/advisories/GHSA-mghf-wjfp-p5xm
CVSS
- Attack Vector
- Network
- Attack Complexity
- Low
- Privileges Required
- Low
- User Interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
What is CVE-2026-115893 Wasmtime Cranelift aarch64 br_table Incorrect Branch Target (CVE-2026-115893)?
Wasmtime Cranelift aarch64 br_table Incorrect Branch Target (CVE-2026-115893) (CVE-2026-115893) maps to the Execution and Privilege Escalation tactics — the adversary is trying to run malicious code or instructions on a system in MITRE ATT&CK.
This page provides production-ready detection logic for Wasmtime Cranelift aarch64 br_table Incorrect Branch Target (CVE-2026-115893), covering the data sources and telemetry it touches: Microsoft Defender for Endpoint, DeviceProcessEvents. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
- Tactic
- Execution Privilege Escalation
// df00tech DF00-5b8ad4c8d4 · https://df00tech.com/detections/CVE-2026-115893 · licence: https://df00tech.com/detections/licence
// Detect vulnerable Wasmtime versions on aarch64 hosts and untrusted Wasm compilation
let VulnerableWasmtime = DeviceProcessEvents
| where Timestamp > ago(30d)
| where DeviceType in~ ("Server","Workstation") or isnotempty(DeviceId)
| where ProcessVersionInfoProductName has "wasmtime" or FileName in~ ("wasmtime","wasmtime.exe") or ProcessCommandLine has "wasmtime"
| extend Ver = extract(@"(\d+\.\d+\.\d+)", 1, ProcessVersionInfoProductVersion)
| extend Major = toint(extract(@"^(\d+)\.", 1, Ver)), Minor = toint(extract(@"^\d+\.(\d+)\.", 1, Ver)), Patch = toint(extract(@"^\d+\.\d+\.(\d+)", 1, Ver))
| where isnotempty(Ver)
| where (Major < 36) or (Major == 36 and Patch < 19) or (Major between (37 .. 47)) or (Major == 48 and Patch < 7) or (Major == 49 and Patch < 4)
| project Timestamp, DeviceName, FileName, Ver, ProcessCommandLine, AccountName, InitiatingProcessFileName;
VulnerableWasmtime Finds processes running vulnerable Wasmtime versions (parsed from product version) on hosts, matching the CVE-2026-115893 affected ranges. Pair with crash telemetry for exploitation signal.
Data Sources
Required Tables
False Positives
- aarch64 inventory where Wasmtime is patched but version string not updated in embedded metadata
- Development/test hosts intentionally running old Wasmtime for regression testing
- Static-linked embeddings where the Wasmtime version is not reflected in ProcessVersionInfoProductVersion and must be confirmed via SBOM
Query fingerprint DF00-5b8ad4c8d4 · licence
Sigma logsource & community rules
The detection logic for Wasmtime Cranelift aarch64 br_table Incorrect Branch Target (CVE-2026-115893) (CVE-2026-115893) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
category: process_creation
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2026-115893
References (7)
- https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-mghf-wjfp-p5xm
- https://nvd.nist.gov/vuln/detail/CVE-2026-115893
- https://rustsec.org/advisories/RUSTSEC-2026-0379.html
- https://github.com/bytecodealliance/wasmtime/releases/tag/v36.0.19
- https://github.com/bytecodealliance/wasmtime/releases/tag/v48.0.7
- https://github.com/bytecodealliance/wasmtime/releases/tag/v49.0.4
- https://github.com/bytecodealliance/wasmtime/pull/14818
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are further down this page.
- Test 1 Enumerate installed Wasmtime version
Expected signal: Process execution event for wasmtime with version string in command output.
- Test 2 Scan Rust project dependencies for vulnerable wasmtime
Expected signal: cargo-audit process execution reporting the advisory and the resolved wasmtime version.
- Test 3 Compile a large br_table Wasm module (lab trigger)
Expected signal: Wasmtime compile process event on aarch64; possible abnormal exit code, segfault, or crash log.
Response Playbook
Triage
- Confirm host architecture is aarch64 (arm64); the bug is only reachable on the Cranelift aarch64 backend, so non-aarch64 hosts are not exploitable by this specific flaw.
- Extract the exact Wasmtime version from the binary/crate (e.g. wasmtime --version, Cargo.lock, or SBOM) and compare against affected ranges: < 36.0.19, 37.0.0-48.0.6, 49.0.0-49.0.3.
- Identify whether the embedding compiles untrusted/attacker-supplied Wasm modules at runtime; a module with a very large br_table is the trigger, so attacker-controlled module input is the key risk factor.
- Review recent crash/segfault telemetry or abnormal control-flow faults in the embedding process that correlate with compilation of new modules.
Containment
- Upgrade Wasmtime to a fixed release: 36.0.19, 48.0.7, or 49.0.4 (or later) across all aarch64 hosts, then rebuild/redeploy embeddings.
- As an interim mitigation where upgrade is not immediate, disable acceptance/compilation of untrusted Wasm modules, or restrict br_table size via module validation/pre-screening, or run the embedding on a non-aarch64 host.
- Isolate hosts that compile attacker-supplied modules behind stricter sandboxing (seccomp, separate process, resource limits) until patched.
Evidence Collection
- Capture the Wasmtime version, build flags (Cranelift backend confirmation), and host architecture for each affected deployment.
- Preserve any Wasm modules submitted around the time of suspected exploitation, plus core dumps/crash logs from the embedding process for offline analysis.
Escalation Criteria
- ! Escalate to IR if a vulnerable aarch64 host that compiles untrusted modules shows crashes, unexpected syscalls, or memory-corruption indicators coincident with module submission.
- ! Escalate to the application/platform owner if SBOM scanning reveals the vulnerable Wasmtime dependency in any production service accepting external Wasm.
Investigation Guide
Forensic Artifacts
- >
Wasmtime version metadata in binaries, Cargo.lock, and SBOM entries - >
Submitted Wasm module blobs and their br_table target counts - >
Process core dumps / crash signatures from the embedding process - >
Host architecture inventory flagging aarch64 nodes
Tuning Guidance
Gate alerts on host architecture (aarch64) and on whether the embedding compiles untrusted modules - static trusted-only module workloads are lower risk. Suppress hosts confirmed patched (>=36.0.19 / >=48.0.7 / >=49.0.4) via SBOM. Because version strings are often absent from statically embedded Wasmtime, supplement process telemetry with SBOM/dependency scanning (cargo-audit/RUSTSEC-2026-0379) to avoid false negatives rather than relying on runtime version parsing alone.
Hunting Queries
Inventory all Wasmtime versions per host to scope affected aarch64 deployments against the CVE-2026-115893 ranges.
// df00tech DF00-5b8ad4c8d4 · https://df00tech.com/detections/CVE-2026-115893 · licence: https://df00tech.com/detections/licence
DeviceProcessEvents | where FileName has "wasmtime" | summarize count() by DeviceName, ProcessVersionInfoProductVersion | order by DeviceName asc ``` df00tech DF00-5b8ad4c8d4 · https://df00tech.com/detections/CVE-2026-115893 · licence: https://df00tech.com/detections/licence ```
index=endpoint process=*wasmtime* | stats count by host, version | sort host Atomic Red Team Tests
Query the Wasmtime CLI/binary for its version to determine exposure to CVE-2026-115893.
Command
wasmtime --version || cargo install --list | grep -i wasmtime Cleanup
echo 'no cleanup required' Expected Telemetry
Process execution event for wasmtime with version string in command output.
Expected Detection
Version falls within an affected range (< 36.0.19, 37.0.0-48.0.6, 49.0.0-49.0.3) -> flagged vulnerable.
Use cargo-audit against RUSTSEC-2026-0379 to detect a vulnerable wasmtime crate in a project's Cargo.lock.
Command
cargo audit 2>&1 | grep -i -A3 'RUSTSEC-2026-0379\|wasmtime' Cleanup
echo 'no cleanup required' Expected Telemetry
cargo-audit process execution reporting the advisory and the resolved wasmtime version.
Expected Detection
cargo-audit reports RUSTSEC-2026-0379 for a wasmtime version in the affected range.
In an isolated lab, feed a Wasm module containing a very large br_table to a vulnerable Wasmtime on aarch64 to observe miscompilation/crash behavior.
Command
wasmtime compile ./large_br_table.wasm -o /tmp/out.cwasm; echo exit=$? Cleanup
rm -f /tmp/out.cwasm Expected Telemetry
Wasmtime compile process event on aarch64; possible abnormal exit code, segfault, or crash log.
Expected Detection
Vulnerable Wasmtime on aarch64 compiling an untrusted large-br_table module -> high-risk correlation; crash telemetry escalates.
Related Detections
Tactic Hubs
Related Techniques
Same Tactic: Execution
Blog posts about this detection
Browse by tactic
- Reconnaissance TA0043
- Resource Development TA0042
- Initial Access TA0001
- Execution TA0002
- Persistence TA0003
- Privilege Escalation TA0004
- Stealth TA0005
- Defense Impairment TA0112
- Credential Access TA0006
- Discovery TA0007
- Lateral Movement TA0008
- Collection TA0009
- Command and Control TA0011
- Exfiltration TA0010
- Impact TA0040