VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

wasmtime-jit-debug: vulnerability history, versions and safety

wasmtime-jit-debug is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 81 releases, from Jul 2024 to Jun 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all wasmtime-jit-debug vulnerabilities

Vulert verdict on wasmtime-jit-debug 34.0.2 i

Updated on 23 Oct 2026

Good news: 34.0.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 78/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

What to do: Stay on 34.0.2 or newer. This can change: a vulnerability disclosed tomorrow can affect 34.0.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 34.0.2 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 17 Jun 2025 i
  • Highest CVSS 5.5 i
  • With no published fix 0 i
  • Stars 18,741 i
  • OpenSSF scorecard 6/10 i
  • Last release 15 months ago i
  • Licence Apache-2.0 WITH LLVM-exception i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for wasmtime-jit-debug, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
24.0.13 20 Aug 2026 none Apache-2.0 WITH LLVM-exception — Details →
24.0.12 31 Jul 2026 none Apache-2.0 WITH LLVM-exception — Details →
24.0.11 24 Jun 2026 none Apache-2.0 WITH LLVM-exception — Details →
24.0.10 15 Jun 2026 none Apache-2.0 WITH LLVM-exception — Details →
24.0.9 21 May 2026 none Apache-2.0 WITH LLVM-exception — Details →
24.0.8 30 Apr 2026 none Apache-2.0 WITH LLVM-exception — Details →
24.0.7 09 Apr 2026 none Apache-2.0 WITH LLVM-exception — Details →
24.0.6 24 Feb 2026 none Apache-2.0 WITH LLVM-exception — Details →
24.0.5 11 Nov 2025 none Apache-2.0 WITH LLVM-exception — Details →
33.0.2 18 Jul 2025 none Apache-2.0 WITH LLVM-exception — Details →
34.0.2 18 Jul 2025 none Apache-2.0 WITH LLVM-exception — Details →
24.0.4 18 Jul 2025 none Apache-2.0 WITH LLVM-exception — Details →
33.0.1 24 Jun 2025 none Apache-2.0 WITH LLVM-exception — Details →
34.0.1 24 Jun 2025 none Apache-2.0 WITH LLVM-exception — Details →
24.0.3 24 Jun 2025 none Apache-2.0 WITH LLVM-exception — Details →
32.0.1 24 Jun 2025 none Apache-2.0 WITH LLVM-exception — Details →
34.0.0 20 Jun 2025 none Apache-2.0 WITH LLVM-exception — Details →
33.0.0 20 May 2025 none Apache-2.0 WITH LLVM-exception — Details →
32.0.0 21 Apr 2025 none Apache-2.0 WITH LLVM-exception — Details →
31.0.0 20 Mar 2025 none Apache-2.0 WITH LLVM-exception — Details →
30.0.2 25 Feb 2025 none Apache-2.0 WITH LLVM-exception — Details →
30.0.1 21 Feb 2025 none Apache-2.0 WITH LLVM-exception — Details →
30.0.0 20 Feb 2025 none Apache-2.0 WITH LLVM-exception — Details →
29.0.1 21 Jan 2025 none Apache-2.0 WITH LLVM-exception — Details →
29.0.0 20 Jan 2025 none Apache-2.0 WITH LLVM-exception — Details →
28.0.1 14 Jan 2025 none Apache-2.0 WITH LLVM-exception — Details →
28.0.0 20 Dec 2024 none Apache-2.0 WITH LLVM-exception — Details →
27.0.0 20 Nov 2024 none Apache-2.0 WITH LLVM-exception — Details →
25.0.3 05 Nov 2024 none Apache-2.0 WITH LLVM-exception — Details →
26.0.1 05 Nov 2024 none Apache-2.0 WITH LLVM-exception — Details →
24.0.2 05 Nov 2024 none Apache-2.0 WITH LLVM-exception — Details →
26.0.0 22 Oct 2024 none Apache-2.0 WITH LLVM-exception — Details →
23.0.3 09 Oct 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
22.0.1 09 Oct 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
21.0.2 09 Oct 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
24.0.1 09 Oct 2024 none Apache-2.0 WITH LLVM-exception — Details →
25.0.2 09 Oct 2024 none Apache-2.0 WITH LLVM-exception — Details →
25.0.1 24 Sep 2024 none Apache-2.0 WITH LLVM-exception — Details →
25.0.0 20 Sep 2024 none Apache-2.0 WITH LLVM-exception — Details →
24.0.0 20 Aug 2024 none Apache-2.0 WITH LLVM-exception — Details →
23.0.2 12 Aug 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
23.0.1 22 Jul 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
23.0.0 22 Jul 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
22.0.0 20 Jun 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
21.0.1 22 May 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
21.0.0 20 May 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
20.0.2 07 May 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
20.0.1 03 May 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
20.0.0 22 Apr 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
17.0.3 11 Apr 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
19.0.2 11 Apr 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
18.0.4 11 Apr 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
19.0.1 02 Apr 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
19.0.0 20 Mar 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
18.0.3 12 Mar 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
18.0.2 28 Feb 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
17.0.2 28 Feb 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
18.0.1 20 Feb 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
18.0.0 20 Feb 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
17.0.1 07 Feb 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
17.0.0 25 Jan 2024 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
16.0.0 20 Dec 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
15.0.1 01 Dec 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
15.0.0 20 Nov 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
14.0.4 01 Nov 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
14.0.3 30 Oct 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
14.0.2 26 Oct 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
13.0.1 26 Oct 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
14.0.1 23 Oct 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
14.0.0 20 Oct 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
13.0.0 20 Sep 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
12.0.2 14 Sep 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
11.0.2 14 Sep 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
10.0.2 14 Sep 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
12.0.1 24 Aug 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
12.0.0 21 Aug 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
11.0.1 24 Jul 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
11.0.0 20 Jul 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
10.0.1 21 Jun 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
10.0.0 20 Jun 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
9.0.4 13 Jun 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
9.0.3 31 May 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
9.0.2 26 May 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
9.0.1 22 May 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
9.0.0 22 May 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
7.0.1 27 Apr 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
8.0.1 27 Apr 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
6.0.2 27 Apr 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
8.0.0 20 Apr 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
7.0.0 20 Mar 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
6.0.1 08 Mar 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
4.0.1 08 Mar 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
5.0.1 08 Mar 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
6.0.0 20 Feb 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
5.0.0 20 Jan 2023 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
4.0.0 21 Dec 2022 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
3.0.1 01 Dec 2022 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
3.0.0 21 Nov 2022 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
1.0.2 11 Nov 2022 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
2.0.2 10 Nov 2022 M1 U1 Apache-2.0 WITH LLVM-exception Yes Details →
2.0.1 27 Oct 2022 M1 U1 — Yes Details →
2.0.0 20 Oct 2022 M1 U1 — Yes Details →
1.0.1 26 Sep 2022 M1 U1 — Yes Details →
1.0.0 20 Sep 2022 M1 U1 — Yes Details →
0.40.1 31 Aug 2022 M1 U1 — Yes Details →
0.40.0 22 Aug 2022 M1 U1 — Yes Details →
0.39.1 21 Jul 2022 M1 U1 — Yes Details →
0.38.3 21 Jul 2022 M1 U1 — Yes Details →
0.38.2 20 Jul 2022 M1 U1 — Yes Details →
0.39.0 20 Jul 2022 M1 U1 — Yes Details →
0.38.1 27 Jun 2022 M1 U1 — Yes Details →
0.38.0 21 Jun 2022 M1 U1 — Yes Details →
0.37.0 20 May 2022 M1 U1 — Yes Details →
0.36.0 20 Apr 2022 M1 U1 — Yes Details →
0.35.3 11 Apr 2022 M1 U1 — Yes Details →
0.35.2 31 Mar 2022 M1 U1 — Yes Details →
0.35.1 09 Mar 2022 M1 U1 — Yes Details →
0.35.0 07 Mar 2022 M1 U1 — Yes Details →

All 118 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for wasmtime-jit-debug

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Memory Leak Vulnerability in wasmtime_jit_debug: Unsafe Memory Dumping 5.5 medium 24.0.0 17 Jun 2025
Memory Exposure Vulnerability in wasmtime-jit-debug: Dump Undefined Memory by JitDumpFile N/A unrated 24.0.0 06 Jul 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About wasmtime-jit-debug

Is wasmtime-jit-debug safe to use?

Vulert records 2 vulnerabilities for wasmtime-jit-debug in crates.io: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is wasmtime-jit-debug's Vulert package health score?

Vulert scores wasmtime-jit-debug 78/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of wasmtime-jit-debug affected?

No. 34.0.2, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of wasmtime-jit-debug should I use?

34.0.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does wasmtime-jit-debug have?

2 vulnerabilities are recorded for wasmtime-jit-debug in the crates.io ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new wasmtime-jit-debug vulnerabilities disclosed?

0 vulnerabilities were recorded for wasmtime-jit-debug in the last 12 months, and the oldest entry in this database dates to 06 Jul 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of wasmtime-jit-debug are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor wasmtime-jit-debug for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the wasmtime-jit-debug version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.