Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.5

wasmtime_jit_debug Dumps Undefined Memory by JitDumpFile

GHSA-9ghp-w2hm-vfpf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (wasmtime-jit-debug 24.0.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.5 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

The unsound function dumpcodeloadrecord uses fromrawparts 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 dumpcodeloadrecord 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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-9ghp-w2hm-vfpf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-9ghp-w2hm-vfpf

Advisory: wasmtime_jit_debug Dumps Undefined Memory by `JitDumpFile`
IDs: GHSA-9ghp-w2hm-vfpf
Record: https://patchnext.com/advisories/ghsa-9ghp-w2hm-vfpf (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: wasmtime-jit-debug 24.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io wasmtime-jit-debug: affected < 24.0.0; fixed in 24.0.0

## Suggested inspection (read-only)
- crates.io wasmtime-jit-debug: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wasmtime-jit-debug.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9ghp-w2hm-vfpf (GitHub-reviewed advisory GHSA-9ghp-w2hm-vfpf lists affected ranges: crates.io wasmtime-jit-debug >=0 <24.0.0)

Commands are suggestions: review each one before running it.

Loading voting…