CVE-2022-39392

MEDIUMNVD 5.95.9
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.7% (51st 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
5.9EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Wasmtime is a standalone runtime for WebAssembly. Prior to version 2.0.2, there is a bug in Wasmtime's implementation of its pooling instance allocator when the allocator is configured to give WebAssembly instances a maximum of zero pages of memory. In this configuration, the virtual memory mapping for WebAssembly memories did not meet the compiler-required configuration requirements for safely executing WebAssembly modules. Wasmtime's default settings require virtual memory page faults to indicate that wasm reads/writes are out-of-bounds, but the pooling allocator's configuration would not create an appropriate virtual memory mapping for this meaning out of bounds reads/writes can successfully read/write memory unrelated to the wasm sandbox within range of the base address of the memory mapping created by the pooling allocator. This bug is not applicable with the default settings of the wasmtime crate. This bug can only be triggered by setting InstanceLimits::memory_pages to zero. This is expected to be a very rare configuration since this means that wasm modules cannot allocate any pages of linear memory. All wasm modules produced by all current toolchains are highly likely to use linear memory, so it's expected to be unlikely that this configuration is set to zero by any production embedding of Wasmtime. This bug has been patched and users should upgrade to Wasmtime 2.0.2. This bug can be worked around by increasing the memory_pages allotment when configuring the pooling allocator to a value greater than zero. If an embedding wishes to still prevent memory from actually being used then the Store::limiter method can be used to dynamically disallow growth of memory beyond 0 bytes large. Note that the default memory_pages value is greater than zero.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/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)
Severity59% × 45%
Impact severity (EG Severity): CVSS 5.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.
EPSS PROB
0.7%
EPSS %ILE
51st
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 (5.9): severity, escalated by confirmed exploitation. This CVE's 5.9 is its impact severity (EG Severity), not escalated.

EG Severity
5.9 MEDIUMCVSS-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.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

November 10, 2022

Last Modified

November 21, 2024

References (2)

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
wasmtime—
  • 2.0.0 up to 2.0.2: fixed in 2.0.2
  • every version up to 1.0.2: fixed in 1.0.2
  • 0.0.0-0 up to 1.0.2: fixed in 1.0.2
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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 93 of 196 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-39392?
CVE-2022-39392 is a medium-severity vulnerability; its CVE record was published on November 10, 2022. Wasmtime is a standalone runtime for WebAssembly. Prior to version 2.0.2, there is a bug in Wasmtime's implementation of its pooling instance allocator when the allocator is configured to give WebAssembly instances a maximum of zero pages of memory. In this configuration, the virtual memory mapping…
When was the CVE record for CVE-2022-39392 published?
The CVE record for CVE-2022-39392 was published on November 10, 2022. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2022-39392 actively exploited?
CVE-2022-39392 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-39392?
CVE-2022-39392 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2022-39392?
A fix for CVE-2022-39392 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-2022-39392

Explore →

Is Your Infrastructure Affected by CVE-2022-39392?

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

Book a Demo →Browse All CVEs