CRITICAL CVSS 9.9
Published: 2026-04-09

CVE-2026-34987

bytecodealliance wasmtime Security Advisory (CVE-2026-34987)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2026-34987?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2026-34987 impacting bytecodealliance wasmtime. Evaluated with CVSS Base Score of 9.9 (CRITICAL).

Original NVD Description

Source: NIST NVD
Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime with its Winch (baseline) non-default compiler backend may allow properly constructed guest Wasm to access host memory outside of its linear-memory sandbox. This vulnerability requires use of the Winch compiler (-Ccompiler=winch). By default, Wasmtime uses its Cranelift backend, not Winch. With Winch, the same incorrect assumption is present in theory on both aarch64 and x86-64. The aarch64 case has an observed-working proof of concept, while the x86-64 case is theoretical and may not be reachable in practice. This Winch compiler bug can allow the Wasm guest to access memory before or after the linear-memory region, independently of whether pre- or post-guard regions are configured. The accessible range in the initial bug proof-of-concept is up to 32KiB before the start of memory, or ~4GiB after the start of memory, independently of the size of pre- or post-guard regions or the use of explicit or guard-region-based bounds checking. However, the underlying bug assumes a 32-bit memory offset stored in a 64-bit register has its upper bits cleared when it may not, and so closely related variants of the initial proof-of-concept may be able to access truly arbitrary memory in-process. This could result in a host process segmentation fault (DoS), an arbitrary data leak from the host process, or with a write, potentially an arbitrary RCE. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
Low (PR:L)
Standard user access required
User Interaction
None (UI:N)
Zero human interaction required
Scope
Changed (S:C)
Impacts components beyond caller authority
Confidentiality
High (C:H)
Total information disclosure
Integrity
High (I:H)
Total modification of target system
Availability
High (A:H)
Total denial of service or shutdown

🎯 Affected Versions Matrix

Affected Product bytecodealliance / wasmtime
Affected Versions *
Weakness Enumeration CWE-125

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2026-34987 impacting bytecodealliance wasmtime.

⚡ Nuclei Detection Template (YAML) cve-2026-34987.yaml
id: cve-2026-34987

info:
  name: bytecodealliance wasmtime - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: critical
  description: |
    Automated signature & scanner for CVE-2026-34987 affecting bytecodealliance wasmtime.
    Evaluation: Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime with its Winch (baseline) non-default compiler backe...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2026-34987
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
    cvss-score: 9.9
    cve-id: CVE-2026-34987
    cwe-id: CWE-125
  tags: cve,cve-2026-34987,bytecodealliance,wasmtime,critical

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "wasmtime"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2026-34987.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2026-34987
# Target: bytecodealliance wasmtime | CVSS: 9.9 (CRITICAL)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2026-34987 (bytecodealliance wasmtime)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against bytecodealliance wasmtime scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2026-34987.sh
# Recommended Remediation & Patching Commands for CVE-2026-34987
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install wasmtime 2>/dev/null || \
sudo dnf upgrade wasmtime 2>/dev/null || \
sudo yum update wasmtime

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i wasmtime 2>/dev/null || rpm -qa | grep -i wasmtime

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

🔗 Verified Technical References

Authorities
  • No records filed in this category.
Distributions
  • No records filed in this category.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2026-34987 in bytecodealliance wasmtime?

Review vendor-specific security notices and update bytecodealliance wasmtime packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2026-34987?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2026-34987?

CVE-2026-34987 is classified with a CVSS 3.1 Base Score of 9.9 (CRITICAL). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
9.9
CRITICAL SEVERITY
CVE ID CVE-2026-34987
Weakness CWE-125
Vendor bytecodealliance
Product wasmtime
Published 2026-04-09
Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H