Clearance Incident Response. Free through May 1, so you have time to patch.Measure in 5 min. Free AssessmentFree Assessment

aviatrix logoAviatrix
Under Active Attack

Executive Summary

In October 2026, the Bytecode Alliance disclosed two critical vulnerabilities in Wasmtime, a widely embedded WebAssembly runtime, both rated 9.9 CVSS. CVE-2026-115889 affects all processor architectures and stems from a 24-bit integer overflow in Cranelift's value-numbering logic that can cause type confusion and sandbox escape in large or crafted modules. CVE-2026-115893 affects ARM64 systems exclusively, exploiting a br_table branch-reach limitation present since 2020 that allows attacker-controlled modules to redirect execution to arbitrary code. Fixed releases (36.0.19, 48.0.7, 49.0.4, 50.0.0) were published October 19–20; unsupported lines received no patch. No active exploitation had been confirmed as of October 26, 2026.

These vulnerabilities highlight a growing supply-chain risk: Wasmtime is embedded as a library inside platforms such as Fastly Compute, serverless frameworks like Spin, and countless Rust-based services. A single unpatched dependency can expose an entire multi-tenant infrastructure to sandbox escape, making dependency hygiene and runtime segmentation critical controls for cloud-native security teams heading into 2027.

Why This Matters Now

WebAssembly runtimes are increasingly embedded in cloud platforms, edge compute, and AI inference pipelines, making sandbox integrity a first-class security property. With two near-perfect CVSS scores, no workarounds available, and Dependabot silent on the ARM64 flaw due to an unreviewed GitHub advisory, organizations running Wasmtime on ARM64 infrastructure—common in AWS Graviton and Ampere Altra deployments—face undetected exposure today unless they audit Cargo.lock files manually with cargo-audit.

Attack Path Analysis

Related CVEs

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

CVE-2026-115889 affects all architectures on versions before 43.0.0 (including the 36.x LTS line before 36.0.19); CVE-2026-115893 affects ARM64 on all versions before the respective fixed releases (36.0.19, 48.0.7, 49.0.4, or 50.0.0). Upgrade to a patched release immediately, and rebuild every application that embeds Wasmtime as a library—updating only the CLI is insufficient.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

Aviatrix Zero Trust CNSF is directly relevant here because a Cranelift sandbox escape gives an attacker host-level reach across co-hosted workloads and cloud credentials, precisely the east-west and egress exposure that identity-aware segmentation and controlled egress policies are designed to constrain. By enforcing workload-scoped access boundaries and restricting outbound paths, CNSF would likely reduce the attacker's ability to pivot across microservices and exfiltrate data undetected.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: CNSF network segmentation would likely limit the exposed attack surface reachable by external untrusted inputs, reducing the set of workloads that could receive and compile malicious Wasm modules from arbitrary external sources.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Zero Trust segmentation policies would likely reduce the credential and identity scope available to a compromised workload by enforcing least-privilege access boundaries at the workload identity level, making it harder for the attacker to leverage harvested credentials across broader cloud resources.

Lateral Movement

Control: East-West Traffic Security

Mitigation: East-west traffic enforcement would likely constrain the attacker's ability to move freely between microservices and internal APIs by restricting inter-workload communication to explicitly permitted paths, reducing the reachability of adjacent services from a single compromised host.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Multicloud visibility and centralized traffic control would likely make outbound command-and-control beaconing more detectable and reducible by surfacing anomalous egress flows from workloads that have no legitimate reason to contact external infrastructure.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Egress security and policy enforcement would likely reduce the attacker's ability to exfiltrate data to arbitrary external destinations by restricting outbound traffic from sensitive workloads to a defined set of permitted endpoints and protocols.

Impact (Mitigations)

With segmentation and egress controls reducing lateral movement and outbound data transfer paths, the attacker's overall blast radius would likely be constrained to the initially compromised workload's identity scope rather than spreading across the full multi-tenant platform or cloud account.

Impact at a Glance

Affected Business Functions

  • Serverless and Edge Compute Platforms (e.g., Fastly Compute, Fermyon Spin)
  • WebAssembly-based Multi-Tenant Code Execution Services
  • Cloud-Native Application Runtime Infrastructure
  • Supply Chain Integrity for Rust/WebAssembly Software Ecosystems
Operational Disruption

Estimated downtime: 1 days

Financial Impact

Estimated loss: N/A

Data Exposure

No confirmed data exfiltration or breach has been reported. However, the sandbox escape primitives exposed by both CVEs theoretically allow a malicious WebAssembly module operator to access host memory, host process data, and any secrets or tenant data resident in the host environment at the time of exploitation. In multi-tenant platforms such as Fastly Compute, this could include co-tenant application secrets, cryptographic keys, environment variables, and in-flight request payloads. The actual data at risk depends entirely on the host application and deployment context. No exploitation has been confirmed in the wild as of October 26, 2026.

Recommended Actions

  • • Immediately patch all Wasmtime-embedded applications to fixed releases (36.0.19, 48.0.7, 49.0.4, or 50.0.0) and rebuild any program that statically links Wasmtime as a library, as updating only the CLI is insufficient; use cargo-audit with RustSec entries RUSTSEC-2026-0380 and RUSTSEC-2026-0379 to identify affected Cargo.lock dependencies across the supply chain.
  • • Apply Zero Trust Segmentation (CNSF East-West Traffic Security and Zero Trust Segmentation capabilities) to enforce identity-based, least-privilege policies between Wasmtime host workloads and adjacent microservices, preventing a sandbox escapee from pivoting laterally to internal APIs, databases, or cross-namespace Kubernetes resources.
  • • Deploy Egress Security and Cloud Firewall (ACF) controls with FQDN filtering and outbound policy enforcement on all compute nodes running Wasmtime-based services to block unauthorized command-and-control callbacks and data exfiltration channels that an escaped module would attempt to establish over standard HTTPS egress.
  • • Enable Multicloud Visibility and Threat Detection controls to baseline normal traffic patterns from Wasmtime host processes and alert on anomalous outbound connections, unexpected process-level network activity, or unusual cloud API calls originating from serverless or container workloads that compile untrusted Wasm modules.
  • • Enforce Inline IPS (Suricata) inspection on egress paths from Wasm-hosting workloads to detect and block known exploit payload signatures and malicious post-exploitation traffic patterns, and ensure the CNSF fabric provides real-time distributed policy enforcement so that even if a sandbox escape occurs, subsequent attacker actions are intercepted before data can be exfiltrated or impact achieved.

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Stop Advanced ThreatsFree Containment AssessmentUnder Active Attack?
Cta pattren Image