CVE-2026-47261

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% 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, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Wasmtime is a runtime for WebAssembly. In versions prior to 24.0.9, 36.0.10, and 44.0.2, when a filesystem preopen is given DirPerms::all() and FilePerms::READ without FilePerms::WRITE, this access control mechanism can be bypassed via the wasip2 descriptor.open-at or wasip1 path_open interfaces by opening a file with only the OpenFlags::TRUNCATE oflag. The root cause is that the clause handling OpenFlags::TRUNCATE in crates/wasi/src/filesystem.rs (Dir::open_at, lines 967–969) did not set open_mode |= OpenMode::WRITE;, which is later used for the access control check against FilePerms to determine whether opening the file is permitted; the single-line fix adds that missing assignment, after which the affected calls correctly fail with error-code.not-permitted and ERRNO_PERM respectively. Only wasmtime-wasi embeddings that combine DirPerms::MUTATE with FilePerms::READ are affected by this bug. In particular, the Wasmtime project's wasmtime-cli's use of wasmtime-wasi is not affected, because it always sets FilePerms::all() for all preopens. This issue has been fixed in versions 24.0.9, 36.0.10 and44.0.2.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
27.8%
KEV
Not listed

Published

June 5, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Jun 15, 2026
Patch available. Sources: github_release, github.
github Patch Available

WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction · Advisory · bytecodealliance/wasmtime · GitHub

https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-2r75-cxrj-cmph
github_release Patch Available

Release v45.0.0 (bytecodealliance/wasmtime)

Patch available: bytecodealliance/wasmtime v45.0.0

https://github.com/bytecodealliance/wasmtime/releases/tag/v45.0.0
github_release Patch Available

Release v44.0.2 (bytecodealliance/wasmtime)

Patch available: bytecodealliance/wasmtime v44.0.2

https://github.com/bytecodealliance/wasmtime/releases/tag/v44.0.2
github_release Patch Available

Release v36.0.10 (bytecodealliance/wasmtime)

Patch available: bytecodealliance/wasmtime v36.0.10

https://github.com/bytecodealliance/wasmtime/releases/tag/v36.0.10
github_release Patch Available

Release v24.0.9 (bytecodealliance/wasmtime)

Patch available: bytecodealliance/wasmtime v24.0.9

https://github.com/bytecodealliance/wasmtime/releases/tag/v24.0.9

Vendor Advisories for CVE-2026-47261(1)

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

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
wasmtime-wasi—45.0.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 82× 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.

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

Frequently asked(5)

What is CVE-2026-47261?
CVE-2026-47261 is a high vulnerability published on June 5, 2026. Wasmtime is a runtime for WebAssembly. In versions prior to 24.0.9, 36.0.10, and 44.0.2, when a filesystem preopen is given DirPerms::all() and FilePerms::READ without FilePerms::WRITE, this access control mechanism can be bypassed via the wasip2 descriptor.open-at or wasip1 pathopen interfaces by…
When was CVE-2026-47261 disclosed?
CVE-2026-47261 was first published in the National Vulnerability Database on June 5, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47261 actively exploited?
CVE-2026-47261 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47261?
CVE-2026-47261 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-47261?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47261, 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-47261

Explore →

Is Your Infrastructure Affected by CVE-2026-47261?

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

Start Free Scan →Browse All CVEs