How severe is GHSA-9ghp-w2hm-vfpf?

No CVSS score has been assigned to GHSA-9ghp-w2hm-vfpf yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9ghp-w2hm-vfpf?

GHSA-9ghp-w2hm-vfpf affects the following packages: wasmtime-jit-debug (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-9ghp-w2hm-vfpf?

Update wasmtime-jit-debug to 24.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9ghp-w2hm-vfpf is resolved across your whole dependency graph.

How do I detect GHSA-9ghp-w2hm-vfpf in my crates.io dependencies?

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

How do I mitigate GHSA-9ghp-w2hm-vfpf 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.

How does O3 Security protect against GHSA-9ghp-w2hm-vfpf?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9ghp-w2hm-vfpf can be triaged on real exposure rather than presence alone.

Is GHSA-9ghp-w2hm-vfpf actively exploited in the wild?

No public exploit code has been indexed for GHSA-9ghp-w2hm-vfpf 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.

When was GHSA-9ghp-w2hm-vfpf published, and has it been updated?

GHSA-9ghp-w2hm-vfpf was published on June 17, 2025 and was last updated on October 28, 2025. 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

GHSA-9ghp-w2hm-vfpf — wasmtime-jit-debug

Fix: bytecodealliance/wasmtime@b5e31a5

GHSA-9ghp-w2hm-vfpf is a remote code execution vulnerability in wasmtime-jit-debug. A fix is available for wasmtime-jit-debug — see the affected versions and patch details below.

wasmtime_jit_debug Dumps Undefined Memory by `JitDumpFile`

Also known asRUSTSEC-2024-0442

Published

Jun 17, 2025

Updated

Oct 28, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀wasmtime-jit-debug

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

The unsound function dump_code_load_record uses from_raw_parts to directly convert the pointer addr and len into a slice without any validation and that memory block would be dumped.

Thus, the 'safe' function dump_code_load_record is actually 'unsafe' since it requires the caller to guarantee that the addr is valid and len must not overflow. Otherwise, the function could dump the memory into file illegally, causing memory leak.

Note: this is an internal-only crate in the Wasmtime project not intended for external use and is more strongly signaled nowadays as of bytecodealliance/wasmtime#10963. Please open an issue in Wasmtime if you're using this crate directly.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`wasmtime-jit-debug`	all versions	24.0.0`cargo update -p wasmtime-jit-debug --precise 24.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-jit-debug, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wasmtime-jit-debug to 24.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9ghp-w2hm-vfpf 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9ghp-w2hm-vfpf can be triaged on real exposure rather than presence alone.

Tailored to GHSA-9ghp-w2hm-vfpf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The unsound function `dump_code_load_record` uses `from_raw_parts` to directly convert the pointer `addr` and `len` into a slice without any validation and that memory block would be dumped. Thus, the 'safe' function dump_code_load_record is actually 'unsafe' since it requires the caller to guarantee that the addr is valid and len must not overflow. Otherwise, the function could dump the memory into file illegally, causing memory leak. > **Note**: this is an internal-only crate in the Wasmtime project not intended for external use and is more strongly signaled nowadays as of [bytecodeallianc

O3 Security · Impact-Aware SCA

Is GHSA-9ghp-w2hm-vfpf in your dependencies?

O3 Security finds GHSA-9ghp-w2hm-vfpf across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works