CVE-2026-34987

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
9.9
EG Score
9.9(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

April 9, 2026

Last Modified

April 15, 2026

Advisory Details (1)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Wasmtime with Winch compiler backend may allow a sandbox-escaping memory access · Advisory · bytecodealliance/wasmtime · GitHub

https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-xx5w-cvp6-jv83

Affected Packages

(3 across 3 ecosystems)
crates.io(1)
PackageVulnerable rangeFixed inDependents
wasmtime43.0.043.0.1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rust-wasmtime26.0.1+dfsg-10 ... 36.0.9+dfsg-2 (43 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rust-wasmtime26.0.1+dfsg-10 ... 36.0.6+dfsg-7 (34 versions)36.0.7+dfsg-1

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 161 total refreshes for this CVE.

  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 15:01 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 18:38 UTCOSV refresh
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 07:09 UTCEG score recompute
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 05:07 UTCEG score recompute
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-12 19:24 UTCEG score recompute
  9. 2026-08-12 13:50 UTCEPSS rescore
  10. 2026-08-11 19:28 UTCEG score recompute
  11. 2026-08-11 03:00 UTCEG score recompute
  12. 2026-08-11 00:00 UTCEPSS rescore
  13. 2026-08-09 17:29 UTCEG score recompute
  14. 2026-08-09 13:46 UTCEPSS rescore
  15. 2026-08-09 04:34 UTCEG score recompute
  16. 2026-08-08 16:37 UTCEPSS rescore
  17. 2026-08-07 18:55 UTCEG score recompute
  18. 2026-08-06 17:33 UTCEG score recompute
  19. 2026-08-06 13:46 UTCEPSS rescore
  20. 2026-08-05 23:45 UTCEG score recompute
  21. 2026-08-05 19:17 UTCEPSS rescore
  22. 2026-08-04 15:10 UTCEPSS rescore
  23. 2026-08-04 10:38 UTCEPSS rescore
  24. 2026-08-03 22:00 UTCEG score recompute
  25. 2026-08-03 10:36 UTCEPSS rescore
  26. 2026-08-02 13:54 UTCEG score recompute
  27. 2026-08-02 02:27 UTCEPSS rescore
  28. 2026-08-01 04:16 UTCEPSS rescore
  29. 2026-07-30 16:28 UTCEPSS rescore
  30. 2026-07-30 01:30 UTCEPSS rescore
  31. 2026-07-27 14:13 UTCEPSS rescore
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-25 14:18 UTCEPSS rescore
  35. 2026-07-25 14:18 UTCEPSS rescore
  36. 2026-07-24 14:17 UTCEPSS rescore
  37. 2026-07-24 14:17 UTCEPSS rescore
  38. 2026-07-23 14:18 UTCEPSS rescore
  39. 2026-07-23 14:18 UTCEPSS rescore
  40. 2026-07-23 03:10 UTCEG score recompute
  41. 2026-07-22 14:08 UTCEPSS rescore
  42. 2026-07-21 15:24 UTCEPSS rescore
  43. 2026-07-20 20:02 UTCOSV refresh
  44. 2026-07-20 17:08 UTCEPSS rescore
  45. 2026-07-19 14:31 UTCEPSS rescore
  46. 2026-07-19 02:29 UTCEPSS rescore
  47. 2026-07-18 10:04 UTCEPSS rescore
  48. 2026-07-16 17:03 UTCEPSS rescore
  49. 2026-07-15 16:57 UTCEPSS rescore
  50. 2026-07-15 16:57 UTCEPSS rescore
  51. 2026-07-15 02:00 UTCEPSS rescore
  52. 2026-07-13 22:30 UTCEPSS rescore
  53. 2026-07-13 06:13 UTCEPSS rescore
  54. 2026-07-13 06:13 UTCEPSS rescore
  55. 2026-07-12 05:46 UTCEPSS rescore
  56. 2026-07-11 08:27 UTCEPSS rescore
  57. 2026-07-09 19:10 UTCEPSS rescore
  58. 2026-07-08 15:15 UTCEPSS rescore
  59. 2026-07-07 13:46 UTCEPSS rescore
  60. 2026-07-06 16:27 UTCEPSS rescore
  61. 2026-07-06 16:27 UTCEPSS rescore
  62. 2026-07-06 02:23 UTCEPSS rescore
  63. 2026-07-06 02:23 UTCEPSS rescore
  64. 2026-07-05 02:30 UTCEPSS rescore
  65. 2026-07-04 06:31 UTCEPSS rescore
  66. 2026-07-01 15:06 UTCEPSS rescore
  67. 2026-06-30 23:22 UTCEPSS rescore
  68. 2026-06-29 14:06 UTCEPSS rescore
  69. 2026-06-29 14:06 UTCEPSS rescore
  70. 2026-06-28 14:07 UTCEPSS rescore
  71. 2026-06-28 14:07 UTCEPSS rescore
  72. 2026-06-28 04:56 UTCEPSS rescore
  73. 2026-06-28 04:56 UTCEPSS rescore
  74. 2026-06-27 03:08 UTCEPSS rescore
  75. 2026-06-25 13:49 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-34987?
CVE-2026-34987 is a critical vulnerability published on April 9, 2026. 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…
When was CVE-2026-34987 disclosed?
CVE-2026-34987 was first published in the National Vulnerability Database on April 9, 2026, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34987 actively exploited?
CVE-2026-34987 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.8% of all scored CVEs.
What is the CVSS score of CVE-2026-34987?
CVE-2026-34987 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-34987?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34987, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-34987

Explore →

Is Your Infrastructure Affected by CVE-2026-34987?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.