Advisory record · GHSA-c2f5-jxjv-2hh8

Wasmtime doesn't fully sandbox all the Windows device filenames

CVSS 2.3 LowEPSS 0.0084 · 57th percentile

Published by the GitHub Advisory Database at 2 Nov 2024, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
wasmtimecrates.io>=0.0.0-0, <24.0.2 || >=25.0.0, <25.0.3 || >=26.0.0, <26.0.124.0.2, 25.0.3, 26.0.1
Identifiers
GHSA-c2f5-jxjv-2hh8 · CVE-2024-51745 · RUSTSEC-2024-0438
Weakness (CWE)
CWE-67 · CWE-184
Published
2 Nov 2024
Updated
12 Oct 2026

Machine-written summary

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

Wasmtime versions before 24.0.2, from 25.0.0 before 25.0.3, and from 26.0.0 before 26.0.1 do not fully sandbox all Windows device filenames. The source gives few details beyond this, so the specific attack conditions are not described. Upgrade to Wasmtime 24.0.2, 25.0.3, 26.0.1, or a later release.

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
2.3 Low 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0084, the 57th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 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.