CVE-2026-35186

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (11th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-21037 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime's Winch compiler backend contains a bug where translating the table.grow operator causes the result to be incorrectly typed. For 32-bit tables this means that the result of the operator, internally in Winch, is tagged as a 64-bit value instead of a 32-bit value. This invalid internal representation of Winch's compiler state compounds into further issues depending on how the value is consumed. The primary consequence of this bug is that bytes in the host's address space can be stored/read from. This is only applicable to the 16 bytes before linear memory, however, as the only significant return value of table.grow that can be misinterpreted is -1. The bytes before linear memory are, by default, unmapped memory. Wasmtime will detect this fault and abort the process, however, because wasm should not be able to access these bytes. Overall this this bug in Winch represents a DoS vector by crashing the host process, a correctness issue within Winch, and a possible leak of up to 16-bytes before linear memory. Wasmtime's default compiler is Cranelift, not Winch, and Wasmtime's default settings are to place guard pages before linear memory. This means that Wasmtime's default configuration is not affected by this issue, and when explicitly choosing Winch Wasmtime's otherwise default configuration leads to a DoS. Disabling guard pages before linear memory is required to possibly leak up to 16-bytes of host data. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 9, 2026

Last Modified

October 26, 2026

Advisory Details (1)

Auto-updated Jun 15, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Improperly masked return value from `table.grow` with Winch compiler backend · Advisory · bytecodealliance/wasmtime · GitHub

https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-f984-pcp8-v2p7

Affected Packages

(3 across 3 ecosystems)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
wasmtime43.0.0
  • 25.0.0 up to 36.0.7: fixed in 36.0.7
  • 37.0.0 up to 42.0.2: fixed in 42.0.2
  • 43.0.0 up to 43.0.1: fixed in 43.0.1
  • 0.0.0-0 up to 36.0.7: fixed in 36.0.7
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-wasmtime26.0.1+dfsg-10 ... 36.0.9+dfsg-2 (43 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rust-wasmtime26.0.1+dfsg-10 ... 36.0.6+dfsg-7 (34 versions)
  • every version up to 36.0.7+dfsg-1: fixed in 36.0.7+dfsg-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 210 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 111 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-35186?
CVE-2026-35186 is a high-severity vulnerability; its CVE record was 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's Winch compiler backend contains a bug where translating the table.grow operator causes the result to be incorrectly typed. For 32-bit tables this means that the result of the operator, internally in…
When was the CVE record for CVE-2026-35186 published?
The CVE record for CVE-2026-35186 was published on April 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-35186 actively exploited?
CVE-2026-35186 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-35186?
CVE-2026-35186 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-35186?
A fix for CVE-2026-35186 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-35186?

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

Book a Demo →Browse All CVEs