Advisory record · GHSA-p8xm-42r7-89xg

Panic when allocating a table exceeding the size of the host's address space

CVSS 5.9 MediumEPSS 0.0032 · 25th percentile

Published by the maintainers · not yet reviewed by GitHub. The bytecodealliance/wasmtime maintainers published this as a GitHub repository advisory; GitHub’s reviewed advisory replaces it here when it arrives.

Published by the bytecodealliance/wasmtime maintainers at 30 Apr 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
wasmtimecrates.io>=30.0.0, <36.0.8 || >=37.0.0, <43.0.2 || >=44.0.0, <44.0.136.0.8, 43.0.2, 44.0.1
Identifiers
GHSA-p8xm-42r7-89xg · CVE-2026-44216 · RUSTSEC-2026-0114
Weakness (CWE)
CWE-190 · CWE-770
Published
30 Apr 2026
Updated
12 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Wasmtime crate is affected in versions 30.0.0 up to 36.0.8, 37.0.0 up to 43.0.2, and 44.0.0 up to 44.0.1. The source gives few details beyond the title, which describes a panic when allocating a table larger than the host's address space. Upgrade to 36.0.8, 43.0.2, or 44.0.1, depending on the release line in use.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.9 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0032, the 25th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 30 Apr 2026, 16:13 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:24 UTC First seen by agentprime
  3. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.