CVE-2026-54786

MEDIUMNVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.0 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% 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
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Wasmtime is a runtime for WebAssembly. All versions prior to 24.0.10; versions 25.0.0 through those before 36.0.11; versions 37.0.0 through those before 44.0.3; and versions 45.0.0 and 45.0.1 contain a native implementation of WASIp1 which suffers from a leak in the fd_renumber function where the file descriptor being renumbered to is not properly closed. Wasmtime's implementation erroneously only updated the table of descriptors for WASIp1 and didn't update the underlying table of descriptors used by the host. This behavior means that while fd_renumber works correctly from a guest's perspective it ends up leaking resources in the host that aren't cleaned up until the corresponding Store is destroyed. In a loop, guests can use fd_renumber to cause hosts to exhaust both resources and file descriptors. This bug only affects the native implementation of WASIp1, meaning that only runtimes which load core wasm modules and expose fd_renumber are affected. Runtimes are additionally only affected if they expose the ability to acquire a file descriptor, such as opening a file. For runtimes that deny access to files they are unaffected. This issue has been fixed in versions 24.0.10, 36.0.11, 44.0.3, and 45.0.2.

CVSS v3
5.0
EG Score
5.0MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100

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
Severity50% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.4%
EPSS %ILE
28th
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jul 7, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

Leak in WASIp1 `fd_renumber` implementation · Advisory · bytecodealliance/wasmtime · GitHub

https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-3p27-qvp9-27qf

Vendor Advisories for CVE-2026-54786(1)

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

Affected Packages

(3 across 3 ecosystems)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
wasmtime-wasi—
  • every version up to 24.0.10: fixed in 24.0.10
  • 45.0.0 up to 45.0.2: fixed in 45.0.2
  • 25.0.0 up to 36.0.11: fixed in 36.0.11
  • 37.0.0 up to 44.0.3: fixed in 44.0.3
  • 0.0.0-0 up to 24.0.10: fixed in 24.0.10
—
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.9+dfsg-2 (38 versions)
  • every version up to 36.0.11+dfsg-1: fixed in 36.0.11+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 / 29× 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 138 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54786?
CVE-2026-54786 is a medium vulnerability published on July 1, 2026. Wasmtime is a runtime for WebAssembly. All versions prior to 24.0.10; versions 25.0.0 through those before 36.0.11; versions 37.0.0 through those before 44.0.3; and versions 45.0.0 and 45.0.1 contain a native implementation of WASIp1 which suffers from a leak in the fdrenumber function where the…
When was CVE-2026-54786 disclosed?
CVE-2026-54786 was first published on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54786 actively exploited?
CVE-2026-54786 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54786?
CVE-2026-54786 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2026-54786?
A fix for CVE-2026-54786 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54786 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54786?

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

Book a Demo →Browse All CVEs