CVE-2026-44216

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Wasmtime is a runtime for WebAssembly. From 30.0.0 to 36.0.8, 43.0.2, and 44.0.1, Wasmtime's allocation logic for a WebAssembly table contained checked arithmetic which panicked on overflow. This overflow is possible to trigger, and thus panic, when a table with an extremely large size is allocated. This is possible with the WebAssembly memory64 proposal where tables can have sizes in the 64-bit range as opposed to the previous 32-bit range which would not overflow. The panic happens when attempting to create a very large table, such as when instantiating a WebAssembly module or component. This vulnerability is fixed in 36.0.8, 43.0.2, and 44.0.1.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

May 14, 2026

Last Modified

July 28, 2026

Advisory Details (1)

Auto-updated May 18, 2026
Patch available. Sources: github.
github Patch Available

Panic when allocating a table exceeding the size of the host's address space · Advisory · bytecodealliance/wasmtime · GitHub

https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-p8xm-42r7-89xg

Vendor Advisories for CVE-2026-44216(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrust-main-1.97.1-2.hum12026-07-24redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
crates.io(1)
PackageVulnerable rangeFixed inDependents
wasmtime—44.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.7+dfsg-1 (35 versions)36.0.8+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 / 33× 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 170 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44216?
CVE-2026-44216 is a high vulnerability published on May 14, 2026. Wasmtime is a runtime for WebAssembly. From 30.0.0 to 36.0.8, 43.0.2, and 44.0.1, Wasmtime's allocation logic for a WebAssembly table contained checked arithmetic which panicked on overflow. This overflow is possible to trigger, and thus panic, when a table with an extremely large size is…
When was CVE-2026-44216 disclosed?
CVE-2026-44216 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44216 actively exploited?
CVE-2026-44216 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 75.3% of all scored CVEs.
What is the CVSS score of CVE-2026-44216?
CVE-2026-44216 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-44216?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44216, 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-44216

Explore →

Is Your Infrastructure Affected by CVE-2026-44216?

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

Start Free Scan →Browse All CVEs