How severe is GHSA-c2f5-jxjv-2hh8?

No CVSS score has been assigned to GHSA-c2f5-jxjv-2hh8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c2f5-jxjv-2hh8?

GHSA-c2f5-jxjv-2hh8 affects the following packages: wasmtime (crates.io), wasmtime (crates.io), wasmtime (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-c2f5-jxjv-2hh8?

Update wasmtime to 24.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c2f5-jxjv-2hh8 is resolved across your whole dependency graph.

How do I detect GHSA-c2f5-jxjv-2hh8 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wasmtime, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-c2f5-jxjv-2hh8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-c2f5-jxjv-2hh8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-c2f5-jxjv-2hh8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-c2f5-jxjv-2hh8?

GHSA-c2f5-jxjv-2hh8 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 58th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-c2f5-jxjv-2hh8?

GHSA-c2f5-jxjv-2hh8 is classified as CWE-67 (CWE-67), CWE-184 (CWE-184). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-c2f5-jxjv-2hh8 published, and has it been updated?

GHSA-c2f5-jxjv-2hh8 was published on November 5, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

Wasmtime doesn't fully sandbox all the Windows device filenamesGHSA-c2f5-jxjv-2hh8

Fix: bytecodealliance/cap-std#371

GHSA-c2f5-jxjv-2hh8 is a CWE-67 vulnerability in wasmtime. A fix is available for wasmtime — see the affected versions and patch details below.

Also known asCVE-2024-51745RUSTSEC-2024-0438

Published

Nov 5, 2024

Updated

Sep 10, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-c2f5-jxjv-2hh8.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🦀wasmtime🦀wasmtime🦀wasmtime

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Wasmtime's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however it did not block access to the special device filenames which use superscript digits, such as "COM¹", "COM²", "LPT⁰", "LPT¹", and so on. Untrusted Wasm programs that are given access to any filesystem directory could bypass the sandbox and access devices through those special device filenames with superscript digits, and through them gain access peripheral devices connected to the computer, or network resources mapped to those devices. This can include modems, printers, network printers, and any other device connected to a serial or parallel port, including emulated USB serial ports.

Patches

Patch releases for Wasmtime have been issued as 24.0.2, 25.0.3, and 26.0.1. Users of Wasmtime 23.0.x and prior are recommended to upgrade to one of these patched versions.

Workarounds

There are no known workarounds for this issue. Affected Windows users are recommended to upgrade.

References

Microsoft's documentation of the special device filenames
ISO-8859-1
The original PR reporting the issue

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`wasmtime`	all versions	24.0.2`cargo update -p wasmtime --precise 24.0.2`
🦀crates.io	`wasmtime`	≥ 25.0.0&&< 25.0.3	25.0.3`cargo update -p wasmtime --precise 25.0.3`
🦀crates.io	`wasmtime`	≥ 26.0.0&&< 26.0.1	26.0.1`cargo update -p wasmtime --precise 26.0.1`

Affected Products

1 product · 5 configurations

Application

wasmtimebytecodealliance

< 24.0.2

4 versions

25.0.025.0.125.0.226.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wasmtime, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wasmtime to 24.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c2f5-jxjv-2hh8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact Wasmtime's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however it did not block access to the special device filenames which use superscript digits, such as "COM¹", "COM²", "LPT⁰", "LPT¹", and so on. Untrusted Wasm programs that are given access to any filesystem directory could bypass the sandbox and access devices through those special device filenames with superscript digits, and through them gain access peripheral devices connected to the computer, or network resources mapped to those